← previous blocknext block →recent activity
Analyzing
Block #85,920,829
14 transactions · 12 stateful · 2026-07-06 06:16:07 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,920,829 · 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
1w06w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x1ae7a08a…22b3
0x065c9d…c394
2 touches
0 conflicts
0x3ee0d949…5b65
0x065c9d…c394
2 touches
0 conflicts
0x882e35b5…464d
0x065c9d…c394
2 touches
0 conflicts
0xa5880cfd…f6d2
0x065c9d…c394
2 touches
0 conflicts
0xbe04be3c…7803
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity