← previous blocknext block →recent activity
Analyzing
Block #87,588,786
34 transactions · 31 stateful · 2026-07-14 00:05:29 UTC
Parallelism
47/100
Blocked
65%
Avg conflicts / tx
3.59
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,588,786 · 34 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w08w19w210w311w412w513w614w715w816w917w1018w1119w1220w1323w325w1432w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
24 touches
66 conflicts
0x875164c2…f8a2
0x34b655…2a6f
24 touches
66 conflicts
0x34d95d94…3a16
0x34b655…2a6f
24 touches
66 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
24 touches
66 conflicts
0x5b145de0…367c
0xc8689a…ee79
22 touches
55 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
22 touches
55 conflicts
0x45a2ce5b…1492
0x34b655…2a6f
22 touches
55 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
91 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity