← previous blocknext block →recent activity
Analyzing
Block #87,714,005
53 transactions · 38 stateful · 2026-07-14 14:02:51 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.75
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,714,005 · 53 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w19w010w114w016w120w221w322w423w524w625w726w827w928w1029w1133w438w540w1143w1344w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
10 touches
10 conflicts
0xb65644e3…33ce
0x34b655…2a6f
8 touches
6 conflicts
0x2385516f…eca5
0x34b655…2a6f
8 touches
6 conflicts
0xdd36917c…b88b
0x34b655…2a6f
8 touches
6 conflicts
0x820b2f6b…9263
0x34b655…2a6f
6 touches
3 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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity