← previous blocknext block →recent activity
Analyzing
Block #85,618,181
12 transactions · 11 stateful · 2026-07-04 20:39:23 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,618,181 · 12 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
1w02w17w210w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ceaec93…7838
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7de96f37…40e3
0x065c9d…c394
3 touches
1 conflict
0xbf207dad…d4b5
0x065c9d…c394
3 touches
1 conflict
0x332683b5…9d9a
0x065c9d…c394
2 touches
0 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
0x05b1b07a…7a99
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 0x6ceaec9343…1e7838
Audit this contract →
← previous block·next block →recent activity