pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,190,536
33 transactions · 25 stateful · 2026-05-12 22:05:22 UTC
Parallelism
82/100
Blocked
64%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,190,536 · 33 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w08w212w013w114w216w318w219w320w422w223w324w528w129w231w432w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x768cffcd…2648
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x41d3bfa5…523e
0x34b655…2a6f
8 touches
6 conflicts
0xd3cec055…367b
0xd32edf…ff58
7 touches
6 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 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: 0x065c9d28…a9c394
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity