pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,300,900
14 transactions · 13 stateful · 2026-05-04 04:06:57 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
1.07
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,300,900 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w28w310w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xbf04f37d…85f2
0x2a68ba…90c5
6 touches
5 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0x58285a17…dda3
0x065c9d…c394
5 touches
3 conflicts
0xb6d6d740…e91a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
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: 0x754704bc…afb603
6 conflicts on slot 0xa1087a5ca6…0a66c4
Audit this contract →
← previous block·next block →recent activity