← previous blocknext block →recent activity
Analyzing
Block #102,060,649
11 transactions · 11 stateful · 2026-09-05 01:59:09 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,060,649 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w17w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd02ebff8…fe31
0x34b655…2a6f
4 touches
1 conflict
0x62bb20db…431e
0x34b655…2a6f
4 touches
1 conflict
0x738d841d…3c29
0x34b655…2a6f
4 touches
1 conflict
0xb19ab730…8ae5
0x34b655…2a6f
4 touches
1 conflict
0xb9a0dde5…9e2b
0x34b655…2a6f
4 touches
1 conflict
0xbca9cb8f…92a3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca544518…82c2
0x34b655…2a6f
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
1 conflict on slot 0xd02ebff8eb…05fe31
Audit this contract →
← previous block·next block →recent activity