← previous blocknext block →recent activity
Analyzing
Block #87,715,887
42 transactions · 34 stateful · 2026-07-14 14:15:30 UTC
Parallelism
67/100
Blocked
68%
Avg conflicts / tx
2.43
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,715,887 · 42 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w17w28w09w117w118w219w320w421w522w623w724w829w830w934w136w1037w239w1140w1241w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
20 touches
45 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
12 touches
15 conflicts
0xc0fb0790…a482
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x87923ecf…1f09
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x0c53719e…0366
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