← previous blocknext block →recent activity
Analyzing
Block #87,626,305
24 transactions · 22 stateful · 2026-07-14 04:16:23 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,626,305 · 24 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
1w02w15w06w17w08w19w210w315w016w217w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x767799cd…f423
0xc8689a…ee79
6 touches
3 conflicts
0x62030a81…91be
0x34b655…2a6f
6 touches
3 conflicts
0x62d2152c…c65a
0x34b655…2a6f
6 touches
3 conflicts
0x845ec8b0…c1af
0x34b655…2a6f
6 touches
3 conflicts
0x8deafb5d…4ce5
0x34b655…2a6f
6 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: Perpl
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity