← previous blocknext block →recent activity
Analyzing
Block #87,497,987
47 transactions · 42 stateful · 2026-07-13 13:57:25 UTC
Parallelism
64/100
Blocked
60%
Avg conflicts / tx
2.43
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,497,987 · 47 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w09w110w217w319w420w521w625w426w727w828w929w1032w1133w1234w135w237w1343w1444w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3688185…9b36
0x34b655…2a6f
18 touches
36 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0001
0xc1ff9f…b0fc
10 touches
10 conflicts
0x3a6290da…e683
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0x7afbac8f…9cad
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 0xc36881859a…c49b36
Audit this contract →
← previous block·next block →recent activity