← previous blocknext block →recent activity
Analyzing
Block #101,839,333
13 transactions · 12 stateful · 2026-09-04 07:19:10 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,839,333 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w18w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe4336ac…92d0
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0xce2afb0d…94be
0x34b655…2a6f
4 touches
1 conflict
0xe0da07e4…ccf2
0x34b655…2a6f
4 touches
1 conflict
0xf36124ad…c08f
0x34b655…2a6f
4 touches
1 conflict
0x02372d42…1871
0x34b655…2a6f
4 touches
1 conflict
0x2163efe4…6584
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 0xfe4336ac0f…d992d0
Audit this contract →
← previous block·next block →recent activity