← previous blocknext block →recent activity
Analyzing
Block #101,894,456
20 transactions · 15 stateful · 2026-09-04 11:56:37 UTC
Parallelism
85/100
Blocked
47%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,894,456 · 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
5w06w07w18w29w110w113w014w117w018w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e273bc0…5dbc
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xb40e601f…bf98
0x34b655…2a6f
6 touches
3 conflicts
0x2aa7be4c…0f84
0x34b655…2a6f
6 touches
3 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
6 touches
3 conflicts
0xd4f6a526…ad10
0x34b655…2a6f
6 touches
3 conflicts
0x3d13406e…eff1
0x34b655…2a6f
6 touches
3 conflicts
0x4dffc33e…068d
0x34b655…2a6f
6 touches
3 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 0x7e273bc033…da5dbc
Audit this contract →
← previous block·next block →recent activity