← previous blocknext block →recent activity
Analyzing
Block #87,627,516
18 transactions · 16 stateful · 2026-07-14 04:24:29 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,627,516 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w37w412w113w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x08330b36…ae29
0x34b655…2a6f
6 touches
3 conflicts
0xbd337aaf…cb5e
0x34b655…2a6f
6 touches
3 conflicts
0xef1cbbb7…8cc8
0x34b655…2a6f
6 touches
3 conflicts
0x50e84e6c…287f
0x34b655…2a6f
4 touches
1 conflict
0x588c5b6a…60d2
0x34b655…2a6f
4 touches
1 conflict
0x6323c5ea…ce8a
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity