← previous blocknext block →recent activity
Analyzing
Block #87,593,500
70 transactions · 55 stateful · 2026-07-14 00:37:01 UTC
Parallelism
73/100
Blocked
71%
Avg conflicts / tx
2.23
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,593,500 · 70 txs across 19 waves · depth 19
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
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w110w111w212w313w414w215w016w117w225w526w654w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0001
0xc1ff9f…b0fc
14 touches
21 conflicts
0xc8b0a5d9…ee69
0xd32edf…ff58
13 touches
21 conflicts
0xc514314c…1aa4
0x34b655…2a6f
12 touches
15 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0x69ce640b…884a
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity