← previous blocknext block →recent activity
Analyzing
Block #99,486,511
18 transactions · 17 stateful · 2026-08-27 01:41:50 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,486,511 · 18 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
1w02w14w05w17w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf498679…7732
0x34b655…2a6f
4 touches
1 conflict
0xb1856468…e84f
0x34b655…2a6f
4 touches
1 conflict
0xcac6b16d…5590
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x42e5184f…4e8b
0x34b655…2a6f
4 touches
1 conflict
0x57a7cf46…25d0
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9fc6ea79…e2dc
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
1 conflict on slot 0xaf49867962…697732
Audit this contract →
← previous block·next block →recent activity