← previous blocknext block →recent activity
Analyzing
Block #85,372,832
14 transactions · 9 stateful · 2026-07-03 17:25:45 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,372,832 · 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
2w05w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1afa00e9…016b
0x065c9d…c394
2 touches
0 conflicts
0x49f87f86…7edd
0x065c9d…c394
2 touches
0 conflicts
0xa395a49a…e610
0x065c9d…c394
2 touches
0 conflicts
0xb760b848…33ab
0x065c9d…c394
2 touches
0 conflicts
0xcbefab27…e2cd
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