← previous blocknext block →recent activity
Analyzing
Block #102,307,912
31 transactions · 27 stateful · 2026-09-05 22:52:27 UTC
Parallelism
90/100
Blocked
26%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,307,912 · 31 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w18w09w121w023w024w125w226w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82b5cdc5…89e3
0x34b655…2a6f
6 touches
3 conflicts
0x502b3ee1…7f7c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x73912233…4583
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0x82b5cdc5ae…b889e3
Audit this contract →
← previous block·next block →recent activity