← previous blocknext block →recent activity
Analyzing
Block #85,321,234
16 transactions · 13 stateful · 2026-07-03 11:41:55 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,321,234 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w18w210w011w112w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xfd6ee516…c124
0x0a4fcb…a602
4 touches
1 conflict
0xec52293e…c52d
0x2185cd…21c7
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x92422ced…8761
0x754704…b603
4 touches
1 conflict
0xb8bd6b97…08a2
0x754704…b603
4 touches
1 conflict
0xf653ebdf…16c7
0x754704…b603
4 touches
1 conflict
0xfd6ee516…c125
0x0a4fcb…a602
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-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity