← previous blocknext block →recent activity
Analyzing
Block #99,480,856
14 transactions · 13 stateful · 2026-08-27 01:13:21 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,480,856 · 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
1w02w13w04w05w16w210w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x904e2bfb…1544
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb31eb7d3…64eb
0xa6afd3…d132
4 touches
1 conflict
0xc21def1b…c24d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xac79a0c7…be0f
0x1b6862…e19c
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 0x904e2bfb75…561544
Audit this contract →
← previous block·next block →recent activity