pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,065,218
10 transactions · 9 stateful · 2026-04-28 10:46:59 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,065,218 · 10 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
1w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ff9e831…6008
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9586fd10…e0e4
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x10b5ff2e…ea9b
0x065c9d…c394
4 touches
1 conflict
0xf5f3a257…0b34
0x065c9d…c394
4 touches
1 conflict
0xd21dfa54…8723
0x065c9d…c394
4 touches
1 conflict
0x1e7084f1…5393
0x065c9d…c394
3 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: 0x065c9d28…a9c394
3 conflicts on slot 0x5ff9e83175…0f6008
Audit this contract →
← previous block·next block →recent activity