← previous blocknext block →recent activity
Analyzing
Block #99,855,956
16 transactions · 15 stateful · 2026-08-28 08:54:31 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,855,956 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w18w29w310w411w513w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b13e91…855d
0x34b655…2a6f
12 touches
15 conflicts
0x9ecf942d…fdb7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0xc1d9f34f…7ce1
0x34b655…2a6f
4 touches
1 conflict
0x7e81c352…1b26
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
15 conflicts on slot 0x91b13e914b…cb855d
Audit this contract →
← previous block·next block →recent activity