← previous blocknext block →recent activity
Analyzing
Block #87,628,991
18 transactions · 12 stateful · 2026-07-14 04:34:22 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,628,991 · 18 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
2w03w14w25w37w08w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2697123c…8526
0x34b655…2a6f
8 touches
6 conflicts
0xf04687a1…5ffa
0x34b655…2a6f
8 touches
6 conflicts
0x805d08cf…3cfc
0x34b655…2a6f
8 touches
6 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x3726966a…669d
0x34b655…2a6f
8 touches
6 conflicts
0xd19c9d38…b459
0x34b655…2a6f
8 touches
6 conflicts
0xed59b1cd…8509
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
6 conflicts on slot 0x2697123ce4…5e8526
Audit this contract →
← previous block·next block →recent activity