← previous blocknext block →recent activity
Analyzing
Block #86,314,080
24 transactions · 19 stateful · 2026-07-08 02:01:26 UTC
Parallelism
88/100
Blocked
26%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,314,080 · 24 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
3w04w110w012w013w114w118w219w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xffa7d0a4…b10a
0x40c49f…2af0
4 touches
1 conflict
0x86bd1b84…5bb5
0x40c49f…2af0
4 touches
1 conflict
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0x0e44970b…b209
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity