← previous blocknext block →recent activity
Analyzing
Block #86,317,373
14 transactions · 11 stateful · 2026-07-08 02:23:26 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,317,373 · 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
1w02w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0xd5d7c7f8…ea4f
0x065c9d…c394
4 touches
1 conflict
0xb64e72a8…8b38
0x065c9d…c394
3 touches
1 conflict
0x25de06c6…c3cf
0x065c9d…c394
3 touches
1 conflict
0x376e6295…26ec
0x065c9d…c394
3 touches
1 conflict
0xbbef2329…c209
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity