← previous blocknext block →recent activity
Analyzing
Block #99,448,760
14 transactions · 13 stateful · 2026-08-26 22:31:44 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,448,760 · 14 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
1w02w13w04w18w09w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1856468…e84f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x641245e3…6323
0xc8689a…ee79
4 touches
1 conflict
0x7a78336e…dd1e
0x34b655…2a6f
4 touches
1 conflict
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0xb185646883…2ae84f
Audit this contract →
← previous block·next block →recent activity