← previous blocknext block →recent activity
Analyzing
Block #87,725,174
24 transactions · 23 stateful · 2026-07-14 15:17:41 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,725,174 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w08w19w210w311w414w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x47d4745e…02bb
0x336ed4…c59c
10 touches
10 conflicts
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x67905f6e…02a1
0x34b655…2a6f
8 touches
6 conflicts
0x9407f89d…82ff
0x34b655…2a6f
8 touches
6 conflicts
0xc4de6652…13f4
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity