← previous blocknext block →recent activity
Analyzing
Block #87,363,037
25 transactions · 24 stateful · 2026-07-12 22:54:53 UTC
Parallelism
76/100
Blocked
67%
Avg conflicts / tx
1.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,363,037 · 25 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
1w02w13w24w35w46w57w58w09w110w211w312w113w218w320w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb36b8448…9a06
0x34b655…2a6f
12 touches
15 conflicts
0xd4e1e65f…5ec0
0xd32edf…ff58
11 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xea2d3331…6e37
0x1b6862…e19c
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 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
15 conflicts on slot 0xb36b844891…269a06
Audit this contract →
← previous block·next block →recent activity