← previous blocknext block →recent activity
Analyzing
Block #85,972,393
40 transactions · 25 stateful · 2026-07-06 12:00:01 UTC
Parallelism
92/100
Blocked
40%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,972,393 · 40 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
2w06w17w111w012w015w218w019w120w221w028w130w131w134w238w039w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x776b206d…6cf9
0x3bd359…433a
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xca0f0668…caf3
0xa6afd3…d132
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0xdc19c8ad…c65c
0x065c9d…c394
4 touches
1 conflict
0x6f58168d…ea24
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
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity