pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,425,892
14 transactions · 11 stateful · 2026-05-04 17:59:47 UTC
Parallelism
86/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,425,892 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1aa
0x8d66a4…3095
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xaf44929c…8968
0xd32edf…ff58
3 touches
1 conflict
0x74a22ee3…7c8e
0x8d66a4…3095
3 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 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
1 conflict on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity