← previous blocknext block →recent activity
Analyzing
Block #99,271,365
6 transactions · 6 stateful · 2026-08-26 07:38:43 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,271,365 · 6 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
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x746bcce3…d0ce
0x34b655…2a6f
4 touches
1 conflict
0xaa76c9db…4925
0x34b655…2a6f
4 touches
1 conflict
0xab60dc09…85e4
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x13d12d78…4c97
0x34b655…2a6f
2 touches
0 conflicts
0x14c4e3ca…edd9
0x34b655…2a6f
2 touches
0 conflicts
0x14c4e3ca…edda
0x34b655…2a6f
2 touches
0 conflicts
0x157dbfb2…4089
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 0x746bcce3fa…c7d0ce
Audit this contract →
← previous block·next block →recent activity