← previous blocknext block →recent activity
Analyzing
Block #87,663,695
53 transactions · 49 stateful · 2026-07-14 08:26:15 UTC
Parallelism
70/100
Blocked
65%
Avg conflicts / tx
2.38
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,663,695 · 53 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w211w012w113w216w017w018w119w220w321w422w523w624w725w842w243w344w452w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xc1ff9f…b0fc
18 touches
36 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xa19aba84…8922
0xa6afd3…d132
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
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: 0xc1ff9fef…f4b0fc
36 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity