← previous blocknext block →recent activity
Analyzing
Block #87,919,464
34 transactions · 32 stateful · 2026-07-15 12:57:16 UTC
Parallelism
50/100
Blocked
66%
Avg conflicts / tx
2.41
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,919,464 · 34 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
1w02w14w05w18w29w312w413w514w617w118w720w821w923w1024w225w327w1028w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xd1952ceb…56be
0x34b655…2a6f
10 touches
10 conflicts
0x8e852ae9…fc5d
0x34b655…2a6f
10 touches
10 conflicts
0xdf7963b5…5eef
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity