pev.One block, wave by wave
analyticsdocs
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,361,012
26 transactions · 17 stateful · 2026-05-13 16:59:07 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,361,012 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w112w214w016w217w218w319w420w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x21d8e673…067b
0x1b6862…e19c
4 touches
1 conflict
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
3 conflicts on slot 0x47b807a243…c53307
Audit this contract →
← previous block·next block →recent activity