← previous blocknext block →recent activity
Analyzing
Block #85,623,040
18 transactions · 14 stateful · 2026-07-04 21:11:40 UTC
Parallelism
89/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,623,040 · 18 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
8w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb91ec5bb…f312
0x065c9d…c394
4 touches
1 conflict
0xdfd1d8c8…18e1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0xb9ea068c…0be7
0x065c9d…c394
3 touches
1 conflict
0x7d1316ee…e4ef
0x065c9d…c394
3 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x4dd1db39…a994
0x188d58…ea8e
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 0xb91ec5bb38…0bf312
Audit this contract →
← previous block·next block →recent activity