← previous blocknext block →recent activity
Analyzing
Block #87,354,843
34 transactions · 31 stateful · 2026-07-12 22:00:07 UTC
Parallelism
88/100
Blocked
42%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,354,843 · 34 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
1w02w03w15w27w38w19w210w017w018w119w220w324w025w127w328w129w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fde64da…aa3e
0x2a68ba…90c5
8 touches
6 conflicts
0xd3ef5630…0de9
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x851145…3f07
8 touches
6 conflicts
0xb8644937…ed09
0x851145…3f07
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x0e9a70ab…e67c
0x34b655…2a6f
8 touches
6 conflicts
0x321eac33…6aca
0x34b655…2a6f
8 touches
6 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 0x0fde64da0b…a5aa3e
Audit this contract →
← previous block·next block →recent activity