pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,627,710
9 transactions · 9 stateful · 2026-05-01 01:17:11 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,627,710 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
6 touches
3 conflicts
0x8afca7b1…ca74
0x065c9d…c394
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x63a9cf42…5efc
0x065c9d…c394
3 touches
1 conflict
0x52317d5c…bc99
0x065c9d…c394
3 touches
1 conflict
0x9856b9ad…bca5
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x00000000…0013
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: 0x7e9d3a8a…4f9fda
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity