← previous blocknext block →recent activity
Analyzing
Block #99,251,453
15 transactions · 15 stateful · 2026-08-26 05:58:27 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,251,453 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w110w211w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab60dc09…85e4
0x34b655…2a6f
6 touches
3 conflicts
0xe28f4511…9220
0x34b655…2a6f
6 touches
3 conflicts
0xf95fa02e…ad51
0x34b655…2a6f
4 touches
1 conflict
0x3db01639…a6bd
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x64275949…d698
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
3 conflicts on slot 0xab60dc0972…4c85e4
Audit this contract →
← previous block·next block →recent activity