← previous blocknext block →recent activity
Analyzing
Block #86,220,168
29 transactions · 24 stateful · 2026-07-07 15:34:21 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.66
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,220,168 · 29 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w211w016w117w018w319w420w521w627w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xc7a15219…7745
0xa6afd3…d132
8 touches
6 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xea13a73c…9feb
0xd32edf…ff58
5 touches
3 conflicts
0xed204e2a…91bf
0xa6afd3…d132
5 touches
3 conflicts
0xff863609…8bcb
0xa6afd3…d132
5 touches
3 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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity