← previous blocknext block →recent activity
Analyzing
Block #86,181,001
16 transactions · 12 stateful · 2026-07-07 11:12:44 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,181,001 · 16 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
1w04w05w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9387b99…e9f4
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa70a8b11…1793
0x065c9d…c394
3 touches
1 conflict
0xb8a3806b…4cce
0x065c9d…c394
3 touches
1 conflict
0x2a063d58…40f1
0x065c9d…c394
2 touches
0 conflicts
0x33c77a22…9552
0x065c9d…c394
2 touches
0 conflicts
0x493e6c7e…67d6
0x065c9d…c394
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 0xf9387b9969…c3e9f4
Audit this contract →
← previous block·next block →recent activity