← previous blocknext block →recent activity
Analyzing
Block #99,320,584
14 transactions · 14 stateful · 2026-08-26 11:46:17 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,320,584 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w07w19w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa366dc41…b2d8
0xa6afd3…d132
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0x8300e996…2a03
0x34b655…2a6f
4 touches
1 conflict
0x04e03897…5a19
0x34b655…2a6f
2 touches
0 conflicts
0x0b1daf3c…cae1
0x34b655…2a6f
2 touches
0 conflicts
0x1aad705d…35d2
0x34b655…2a6f
2 touches
0 conflicts
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0xa366dc411e…d4b2d8
Audit this contract →
← previous block·next block →recent activity