← previous blocknext block →recent activity
Analyzing
Block #99,039,990
16 transactions · 16 stateful · 2026-08-25 12:11:00 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,039,990 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w310w411w012w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
6 touches
3 conflicts
0x85657dc4…6c99
0x40c49f…2af0
4 touches
1 conflict
0xc82f6e2a…66ee
0x40c49f…2af0
4 touches
1 conflict
0xd9850dd7…c2c7
0x40c49f…2af0
4 touches
1 conflict
0xf2714abf…15bd
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x9b2d3bee…8eec
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity