pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,177,280
9 transactions · 8 stateful · 2026-04-28 23:13:27 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,177,280 · 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
2w03w14w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0004
0x8d66a4…3095
6 touches
3 conflicts
0x7f430e47…4cbd
0x8d66a4…3095
5 touches
3 conflicts
0xe96c91d2…32ff
0x8d66a4…3095
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1a6
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1aa
0x8d66a4…3095
3 touches
1 conflict
0x8a35acfb…d1a8
0x8d66a4…3095
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: 0x34b6552d…112a6f
3 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity