← previous blocknext block →recent activity
Analyzing
Block #86,316,044
11 transactions · 9 stateful · 2026-07-08 02:14:33 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,316,044 · 11 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
1w03w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40b849b1…f899
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xc0839fa6…1c8d
0x065c9d…c394
3 touches
1 conflict
0x9ea4471c…a5e3
0x065c9d…c394
3 touches
1 conflict
0x2ad2d5a5…d3bf
0x065c9d…c394
3 touches
1 conflict
0x47615ad8…3848
0x065c9d…c394
3 touches
1 conflict
0x9af7ee0d…c79f
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 0x40b849b11c…90f899
Audit this contract →
← previous block·next block →recent activity