← previous blocknext block →recent activity
Analyzing
Block #99,367,341
13 transactions · 10 stateful · 2026-08-26 15:41:45 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,367,341 · 13 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
2w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b31aacc…313d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xfa0c5188…06f2
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x018da3ff…0784
0x34b655…2a6f
2 touches
0 conflicts
0x049b91b8…cae1
0x34b655…2a6f
2 touches
0 conflicts
0x24b6091e…d294
0x34b655…2a6f
2 touches
0 conflicts
0x2e0627fc…47c0
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 0x6b31aaccee…3c313d
Audit this contract →
← previous block·next block →recent activity