pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,859,903
87 transactions · 72 stateful · 2026-05-06 18:12:05 UTC
Parallelism
80/100
Blocked
81%
Avg conflicts / tx
3.24
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #72,859,903 · 87 txs across 17 waves · depth 17
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
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w110w220w427w331w432w534w635w736w837w968w569w671w1072w573w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0x17606ba6…1b6e
0x754704…b603
20 touches
45 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
18 touches
36 conflicts
0x736c5b69…fb3f
0x34b655…2a6f
18 touches
36 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
18 touches
36 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
18 touches
36 conflicts
0xafd59af5…5257
0xc8689a…ee79
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 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
55 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity