pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,446,295
8 transactions · 8 stateful · 2026-04-30 05:05:18 UTC
Parallelism
50/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #71,446,295 · 8 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
2w03w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x2a84ca97…4adc
0x065c9d…c394
2 touches
0 conflicts
0x5c007b31…1514
0x065c9d…c394
2 touches
0 conflicts
0x798ad915…8c69
0x065c9d…c394
2 touches
0 conflicts
0x8e50b1ad…7101
0x065c9d…c394
2 touches
0 conflicts
0x0249e953…56cf
0x34b655…2a6f
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: 0x2a68ba18…8e90c5
6 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity