← previous blocknext block →recent activity
Analyzing
Block #95,751,049
10 transactions · 9 stateful · 2026-08-13 22:32:06 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,751,049 · 10 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd80d1ef4…667b
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x00933c30…9e4d
0x34b655…2a6f
2 touches
0 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x0f97bf50…c21f
0x34b655…2a6f
2 touches
0 conflicts
0x13d12d78…4c97
0x34b655…2a6f
2 touches
0 conflicts
0x1b4aa556…0d2b
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-MON/USDC
1 conflict on slot 0xd80d1ef494…1e667b
Audit this contract →
← previous block·next block →recent activity