← previous blocknext block →recent activity
Analyzing
Block #87,704,283
40 transactions · 35 stateful · 2026-07-14 12:57:45 UTC
Parallelism
68/100
Blocked
69%
Avg conflicts / tx
2.33
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,704,283 · 40 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w111w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x404533df…b37b
0xd32edf…ff58
15 touches
28 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
14 touches
21 conflicts
0xbf68b5d2…0eba
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
12 touches
15 conflicts
0x4f51d069…d0b4
0x34b655…2a6f
12 touches
15 conflicts
0x67905f6e…02a1
0x34b655…2a6f
12 touches
15 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