← previous blocknext block →recent activity
Analyzing
Block #85,624,297
8 transactions · 7 stateful · 2026-07-04 21:20:03 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,624,297 · 8 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
2w04w15w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0xd7616f56…4439
0x065c9d…c394
4 touches
1 conflict
0x597189ac…6c61
0x065c9d…c394
4 touches
1 conflict
0x725a66eb…bb83
0x065c9d…c394
3 touches
1 conflict
0x6cf685d4…2c55
0x065c9d…c394
3 touches
1 conflict
0x039ad64a…c78f
0x065c9d…c394
3 touches
1 conflict
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
3 conflicts on slot 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity