← previous blocknext block →recent activity
Analyzing
Block #85,161,324
16 transactions · 12 stateful · 2026-07-02 17:56:54 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,161,324 · 16 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
1w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x02a4fa11…9862
0x065c9d…c394
2 touches
0 conflicts
0x2d1cd117…bb5c
0x065c9d…c394
2 touches
0 conflicts
0x6f78a453…8195
0x065c9d…c394
2 touches
0 conflicts
0xb45387fd…8db6
0x065c9d…c394
2 touches
0 conflicts
0xd4ef3802…a65e
0x065c9d…c394
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