← previous blocknext block →recent activity
Analyzing
Block #86,057,787
30 transactions · 24 stateful · 2026-07-06 21:30:29 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,057,787 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w09w010w111w012w117w018w119w020w121w122w123w224w326w227w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0004
0x5afd3e…7620
6 touches
3 conflicts
0x00000000…0005
0x5afd3e…7620
6 touches
3 conflicts
0x5d82c9b5…004c
0x3bd359…433a
6 touches
3 conflicts
0x4039b31f…0f4a
0x754704…b603
6 touches
3 conflicts
0x40b8f0ac…20bb
0x34b655…2a6f
4 touches
1 conflict
0x96fed898…e5ba
0x34b655…2a6f
4 touches
1 conflict
0xd6d040d9…9ae3
0x34b655…2a6f
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity