pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,995,664
32 transactions · 27 stateful · 2026-04-28 03:04:03 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #70,995,664 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w08w09w110w211w312w414w015w116w218w321w122w024w128w329w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ae
0x8d66a4…3095
6 touches
3 conflicts
0x8a35acfb…d1af
0x8d66a4…3095
6 touches
3 conflicts
0x8a35acfb…d1b0
0x8d66a4…3095
6 touches
3 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0x87a380d9…2d04
0x34b655…2a6f
4 touches
1 conflict
0x88ea6e90…96ef
0x34b655…2a6f
4 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: 0xb857c13a…1a9be1
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity