← previous blocknext block →recent activity
Analyzing
Block #87,719,030
22 transactions · 21 stateful · 2026-07-14 14:36:36 UTC
Parallelism
59/100
Blocked
57%
Avg conflicts / tx
1.95
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,719,030 · 22 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w59w610w716w117w219w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x34d95d94…3a16
0x34b655…2a6f
16 touches
28 conflicts
0xc9dce17a…a1a1
0x34b655…2a6f
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
16 touches
28 conflicts
0x875164c2…f8a2
0x34b655…2a6f
15 touches
28 conflicts
0x67905f6e…02a1
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
14 touches
21 conflicts
0x08a63efb…b394
0x34b655…2a6f
12 touches
15 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity