← previous blocknext block →recent activity
Analyzing
Block #101,976,212
11 transactions · 11 stateful · 2026-09-04 18:51:13 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,976,212 · 11 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
2w03w16w07w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb27d87d6…6bf8
0x34b655…2a6f
6 touches
3 conflicts
0x20b12801…b09b
0x34b655…2a6f
4 touches
1 conflict
0x29a58269…011a
0x34b655…2a6f
4 touches
1 conflict
0x2b7caca8…860f
0x34b655…2a6f
4 touches
1 conflict
0x2f17174f…68b4
0x34b655…2a6f
4 touches
1 conflict
0x3a02129f…9eaf
0x34b655…2a6f
4 touches
1 conflict
0x448fdf2a…fab4
0x34b655…2a6f
4 touches
1 conflict
0x46c3c991…3fa1
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
3 conflicts on slot 0xb27d87d6be…e96bf8
Audit this contract →
← previous block·next block →recent activity