← previous blocknext block →recent activity
Analyzing
Block #86,366,516
18 transactions · 14 stateful · 2026-07-08 07:51:27 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,366,516 · 18 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
1w02w13w27w38w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xfa40bb2a…5ef4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa184ebe7…3bdf
0x065c9d…c394
3 touches
1 conflict
0x768a992f…e44b
0x065c9d…c394
3 touches
1 conflict
0x10ab97c9…38e6
0x065c9d…c394
3 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 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity