← previous blocknext block →recent activity
Analyzing
Block #87,919,051
47 transactions · 32 stateful · 2026-07-15 12:54:30 UTC
Parallelism
68/100
Blocked
72%
Avg conflicts / tx
2.04
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,919,051 · 47 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w210w011w121w022w124w225w327w128w429w531w132w233w634w735w336w437w540w841w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
12 touches
15 conflicts
0x4f1ad4b4…e00a
0x34b655…2a6f
10 touches
10 conflicts
0x28c714d9…9438
0xa6afd3…d132
8 touches
6 conflicts
0x5c16527f…628c
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: Perpl
28 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity