← previous blocknext block →recent activity
Analyzing
Block #87,713,469
37 transactions · 34 stateful · 2026-07-14 13:59:14 UTC
Parallelism
51/100
Blocked
65%
Avg conflicts / tx
3.65
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,713,469 · 37 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
2w03w05w16w27w38w49w510w611w712w813w914w1015w1116w1217w1318w1419w1520w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6389d47…9a28
0x34b655…2a6f
28 touches
91 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0x5b145de0…367c
0xc8689a…ee79
24 touches
66 conflicts
0x67905f6e…02a1
0x34b655…2a6f
24 touches
66 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
24 touches
66 conflicts
0x312e4698…54c0
0x34b655…2a6f
22 touches
55 conflicts
0x4ca1448c…9de6
0x34b655…2a6f
21 touches
55 conflicts
0x843ebe60…5b3d
0x34b655…2a6f
10 touches
10 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 0xa6389d470d…f19a28
Audit this contract →
← previous block·next block →recent activity