← previous blocknext block →recent activity
Analyzing
Block #99,810,846
20 transactions · 19 stateful · 2026-08-28 05:06:28 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,810,846 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w110w011w112w213w314w416w119w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e6a8155…9636
0x34b655…2a6f
6 touches
3 conflicts
0xf1e064bb…e40b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbbca708a…981e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x77c4bb4a…4ad3
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 0x6e6a81554a…499636
Audit this contract →
← previous block·next block →recent activity