← previous blocknext block →recent activity
Analyzing
Block #87,613,680
36 transactions · 30 stateful · 2026-07-14 02:51:58 UTC
Parallelism
58/100
Blocked
70%
Avg conflicts / tx
2.56
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,613,680 · 36 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w18w211w312w413w514w615w716w817w918w1019w1121w1225w226w1428w334w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
14 touches
21 conflicts
0x49f75237…44f4
0x34b655…2a6f
14 touches
21 conflicts
0xed59b1cd…8509
0x34b655…2a6f
14 touches
21 conflicts
0xd19c9d38…b459
0x34b655…2a6f
14 touches
21 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
14 touches
21 conflicts
0x75b43fdd…8dc1
0x34b655…2a6f
14 touches
21 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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity