← previous blocknext block →recent activity
Analyzing
Block #86,316,965
15 transactions · 11 stateful · 2026-07-08 02:20:42 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,316,965 · 15 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
4w05w19w010w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x3f8116c8…fbe0
0xd32edf…ff58
3 touches
1 conflict
0xad941efe…e684
0x065c9d…c394
3 touches
1 conflict
0xad941efe…e683
0x065c9d…c394
3 touches
1 conflict
0xc13c8788…560e
0x065c9d…c394
3 touches
1 conflict
0x836874a1…b67f
0x19f079…1d56
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
3 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity