← previous blocknext block →recent activity
Analyzing
Block #86,339,417
16 transactions · 14 stateful · 2026-07-08 04:50:40 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,339,417 · 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0xf31ff5af…f6b6
0xa6afd3…d132
3 touches
1 conflict
0x0b0b44c0…23fb
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0003
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0004
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x9d518cc4…4351
0x0594c7…a3be
2 touches
0 conflicts
0xbfa40844…16ad
0x0594c7…a3be
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 0xef65bff33c…857c9d
Audit this contract →
← previous block·next block →recent activity