← previous blocknext block →recent activity
Analyzing
Block #87,637,448
16 transactions · 15 stateful · 2026-07-14 05:30:55 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,637,448 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w09w110w011w113w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
8 touches
6 conflicts
0x8981596f…d14a
0x34b655…2a6f
8 touches
6 conflicts
0xcc6e2e88…6569
0x34b655…2a6f
8 touches
6 conflicts
0xd19c9d38…b459
0x34b655…2a6f
8 touches
6 conflicts
0xd8675136…9a01
0x34b655…2a6f
8 touches
6 conflicts
0xed59b1cd…8509
0x34b655…2a6f
8 touches
6 conflicts
0x9599eb41…b5d6
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity