← previous blocknext block →recent activity
Analyzing
Block #87,729,273
22 transactions · 20 stateful · 2026-07-14 15:45:07 UTC
Parallelism
73/100
Blocked
35%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,729,273 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w08w19w210w311w415w017w121w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x0e54cdd0…05dd
0x34b655…2a6f
6 touches
3 conflicts
0x1a327e22…8ce2
0x34b655…2a6f
6 touches
3 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
6 touches
3 conflicts
0x5ec64628…72e4
0x34b655…2a6f
6 touches
3 conflicts
0xbf768a2f…f453
0x34b655…2a6f
6 touches
3 conflicts
0x521553ff…d548
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: Perpl
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity