← previous blocknext block →recent activity
Analyzing
Block #87,727,554
49 transactions · 38 stateful · 2026-07-14 15:33:38 UTC
Parallelism
65/100
Blocked
61%
Avg conflicts / tx
2.67
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,727,554 · 49 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w09w010w118w019w120w221w322w423w524w625w726w827w928w1029w1130w1231w1333w545w1447w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0xc4de6652…13f4
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
12 touches
15 conflicts
0x67905f6e…02a1
0x34b655…2a6f
12 touches
15 conflicts
0x84d74093…7808
0x34b655…2a6f
12 touches
15 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
12 touches
15 conflicts
0x9d869c44…33b7
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity