← previous blocknext block →recent activity
Analyzing
Block #86,232,960
19 transactions · 15 stateful · 2026-07-07 16:59:45 UTC
Parallelism
89/100
Blocked
20%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,232,960 · 19 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
2w03w14w013w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b810b27…ba5c
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfbeba7fa…4596
0x065c9d…c394
3 touches
1 conflict
0x8ea27905…04af
0x065c9d…c394
3 touches
1 conflict
0x9a891451…f1c6
0x065c9d…c394
3 touches
1 conflict
0xd1ca0bbd…a15b
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 0x8b810b27ca…aeba5c
Audit this contract →
← previous block·next block →recent activity