pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,454,745
38 transactions · 28 stateful · 2026-05-14 03:23:05 UTC
Parallelism
60/100
Blocked
68%
Avg conflicts / tx
2
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #74,454,745 · 38 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w28w311w415w016w117w218w319w420w523w129w732w1033w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x8a35acfb…d1ab
0x8d66a4…3095
12 touches
15 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
10 touches
14 conflicts
0x9ec1983e…f08f
0x34b655…2a6f
10 touches
10 conflicts
0x7cbd466f…1700
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xab3526…fa38
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity