← previous blocknext block →recent activity
Analyzing
Block #99,476,987
20 transactions · 19 stateful · 2026-08-27 00:53:50 UTC
Parallelism
70/100
Blocked
32%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,476,987 · 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
1w03w14w28w310w012w413w514w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x850f1034…9da4
0x34b655…2a6f
10 touches
10 conflicts
0x8b7fe709…9d99
0x34b655…2a6f
8 touches
6 conflicts
0x9aeb10b4…71d2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5b09bf44…5907
0xa6afd3…d132
4 touches
1 conflict
0x70986451…c6bd
0x34b655…2a6f
4 touches
1 conflict
0x746bcce3…d0ce
0x34b655…2a6f
4 touches
1 conflict
0x334699e2…2dbf
0xa6afd3…d132
3 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
10 conflicts on slot 0x850f10342c…309da4
Audit this contract →
← previous block·next block →recent activity