← previous blocknext block →recent activity
Analyzing
Block #85,806,949
16 transactions · 8 stateful · 2026-07-05 17:37:39 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,806,949 · 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
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x34bde5f6…05d7
0xa6afd3…d132
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xca2926e0…61b5
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
2 touches
0 conflicts
0x08b8e539…b9f9
0x754704…b603
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