pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,478,223
61 transactions · 37 stateful · 2026-05-18 21:23:04 UTC
Parallelism
82/100
Blocked
70%
Avg conflicts / tx
1.67
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #75,478,223 · 61 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w38w615w419w520w121w722w823w626w638w940w1043w752w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
16 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
16 touches
28 conflicts
0x5f77d607…2c84
0x065c9d…c394
14 touches
21 conflicts
0x99f41ebe…ad95
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0018
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0028
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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: 0x34b6552d…112a6f
28 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity