← previous blocknext block →recent activity
Analyzing
Block #101,060,295
20 transactions · 15 stateful · 2026-09-01 13:59:37 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,060,295 · 20 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
1w02w03w16w111w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c75c1de…1b27
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd97b0449…00a0
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x92f41d1f…4258
0xa6afd3…d132
4 touches
1 conflict
0x72eb73d7…3aea
0xa6afd3…d132
3 touches
1 conflict
0x40970e69…da50
0x34ae4d…3fc5
2 touches
0 conflicts
0x8cf3d245…1d0d
0x34ae4d…3fc5
2 touches
0 conflicts
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 0x0c75c1ded3…d51b27
Audit this contract →
← previous block·next block →recent activity