← previous blocknext block →recent activity
Analyzing
Block #100,162,938
12 transactions · 12 stateful · 2026-08-29 10:40:51 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,162,938 · 12 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
1w02w03w16w07w08w19w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71717491…10cf
0xa6afd3…d132
4 touches
1 conflict
0x1e168c8b…6945
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xedee7e09…6888
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0x71717491f3…9810cf
Audit this contract →
← previous block·next block →recent activity