← previous blocknext block →recent activity
Analyzing
Block #86,046,388
11 transactions · 6 stateful · 2026-07-06 20:14:34 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,046,388 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x78936e5f…270f
0x065c9d…c394
4 touches
1 conflict
0xe18cb9ce…e214
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0xde17f93e…dcf7
0x065c9d…c394
3 touches
1 conflict
0x8053a8a9…af0c
0x065c9d…c394
3 touches
1 conflict
0xf7ce7192…ba7f
0x40c49f…2af0
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: MarginAccount
1 conflict on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity