← previous blocknext block →recent activity
Analyzing
Block #87,342,439
15 transactions · 13 stateful · 2026-07-12 20:37:11 UTC
Parallelism
53/100
Blocked
62%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,342,439 · 15 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
1w02w13w24w35w46w07w59w610w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64c0e606…b222
0x34b655…2a6f
10 touches
10 conflicts
0x460a21c2…87f1
0x34b655…2a6f
10 touches
10 conflicts
0xd4726587…6289
0x34b655…2a6f
10 touches
10 conflicts
0xdc921364…4680
0x34b655…2a6f
10 touches
10 conflicts
0x727fbce7…0c80
0x34b655…2a6f
10 touches
10 conflicts
0x67bfbc55…7b2f
0x34b655…2a6f
8 touches
6 conflicts
0x7506443a…4820
0x34b655…2a6f
8 touches
6 conflicts
0x820610fd…1dd4
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: Perpl
10 conflicts on slot 0x64c0e606fc…95b222
Audit this contract →
← previous block·next block →recent activity