← previous blocknext block →recent activity
Analyzing
Block #87,713,893
41 transactions · 37 stateful · 2026-07-14 14:02:06 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
2.44
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,713,893 · 41 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
1w02w14w15w06w17w08w19w010w111w012w113w214w315w416w517w618w724w425w627w128w732w234w837w1238w1339w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
14 touches
21 conflicts
0x909b34ee…b9e3
0x34b655…2a6f
12 touches
15 conflicts
0xa6389d47…9a28
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
10 touches
10 conflicts
0x9407f89d…82ff
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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity