← previous blocknext block →recent activity
Analyzing
Block #87,588,004
19 transactions · 16 stateful · 2026-07-14 00:00:15 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,588,004 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w49w210w311w413w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0e4d476…712c
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x17cc5ec3…ae0e
0x34b655…2a6f
8 touches
6 conflicts
0xb2912a93…235f
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xd2453506…54e4
0x34b655…2a6f
8 touches
6 conflicts
0x26ba619e…edfe
0x34b655…2a6f
8 touches
6 conflicts
0x157dbfb2…4089
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
15 conflicts on slot 0xc0e4d47693…ed712c
Audit this contract →
← previous block·next block →recent activity