← previous blocknext block →recent activity
Analyzing
Block #99,617,517
25 transactions · 22 stateful · 2026-08-27 12:47:34 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,617,517 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w17w09w013w114w016w217w118w319w020w222w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b2d3bee…8eeb
0x34b655…2a6f
8 touches
6 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
8 touches
6 conflicts
0x776d1934…9289
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xd392f9dc…0ae2
0x34b655…2a6f
6 touches
3 conflicts
0xd1203697…1ae0
0x40c49f…2af0
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
6 conflicts on slot 0x9b2d3bee9d…d68eeb
Audit this contract →
← previous block·next block →recent activity