← previous blocknext block →recent activity
Analyzing
Block #87,755,472
42 transactions · 36 stateful · 2026-07-14 18:40:22 UTC
Parallelism
67/100
Blocked
61%
Avg conflicts / tx
1.81
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,755,472 · 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
1w02w03w16w07w112w113w214w317w418w519w620w721w823w124w225w326w429w131w533w235w936w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x9001f549…089d
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd972ea45…48b5
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x9ae859db…2d84
0x34b655…2a6f
8 touches
6 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
8 touches
6 conflicts
0xaa643d44…2122
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity