← previous blocknext block →recent activity
Analyzing
Block #99,480,211
19 transactions · 19 stateful · 2026-08-27 01:10:06 UTC
Parallelism
84/100
Blocked
26%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,480,211 · 19 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
1w02w13w05w06w112w214w016w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9b690f3…d3d2
0x8964d7…10f8
4 touches
1 conflict
0xc9b690f3…d3d3
0x8964d7…10f8
4 touches
1 conflict
0xc9b690f3…d3d6
0x8964d7…10f8
4 touches
1 conflict
0xc9b690f3…d3d7
0x8964d7…10f8
4 touches
1 conflict
0xc9b690f3…d3d9
0x8964d7…10f8
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xc9b690f3a6…c4d3d2
Audit this contract →
← previous block·next block →recent activity