← previous blocknext block →recent activity
Analyzing
Block #85,837,109
14 transactions · 14 stateful · 2026-07-05 20:58:24 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,837,109 · 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
2w04w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x87ee379a…cd9e
0x34b655…2a6f
4 touches
1 conflict
0x4674461a…877f
0x065c9d…c394
2 touches
0 conflicts
0xc43ac373…79f8
0x065c9d…c394
2 touches
0 conflicts
0xd4fe4c4e…900d
0x065c9d…c394
2 touches
0 conflicts
0x63f02672…1cd4
0x0a4fcb…a602
2 touches
0 conflicts
0xdd29cc54…64e3
0x0a4fcb…a602
2 touches
0 conflicts
0x6bd9b2de…7d72
0x0f2610…0edc
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity