pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,332,507
42 transactions · 35 stateful · 2026-05-13 13:49:33 UTC
Parallelism
69/100
Blocked
63%
Avg conflicts / tx
2.45
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #74,332,507 · 42 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w111w012w113w214w315w416w517w618w719w820w921w1022w1123w1236w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
26 touches
78 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x1c389468…6b0e
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a7
0x8d66a4…3095
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
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: 0xab35264b…1cfa38
78 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity