← previous blocknext block →recent activity
Analyzing
Block #101,803,229
12 transactions · 11 stateful · 2026-09-04 04:17:34 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,803,229 · 12 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
1w03w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x9a7a0eb0…f2b2
0x34b655…2a6f
4 touches
1 conflict
0xe7fa4f4d…a2e4
0x34b655…2a6f
4 touches
1 conflict
0xf6dab8d4…ab62
0x34b655…2a6f
4 touches
1 conflict
0x044852f8…a64b
0x34b655…2a6f
2 touches
0 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
2 touches
0 conflicts
0x3d13406e…eff1
0x34b655…2a6f
2 touches
0 conflicts
0x4b6dc617…674c
0x34b655…2a6f
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
1 conflict on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity