← previous blocknext block →recent activity
Analyzing
Block #101,061,160
13 transactions · 12 stateful · 2026-09-01 14:03:58 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,061,160 · 13 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
1w04w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb26ff3de…9352
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x89ac61bf…9443
0x34b655…2a6f
4 touches
1 conflict
0xf20aecd4…b723
0x34b655…2a6f
2 touches
0 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
2 touches
0 conflicts
0x2c2761c0…476e
0x34b655…2a6f
2 touches
0 conflicts
0x31454c3b…2c59
0x34b655…2a6f
2 touches
0 conflicts
0x4534366a…8508
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 0xb26ff3ded7…a89352
Audit this contract →
← previous block·next block →recent activity