pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,998,973
8 transactions · 7 stateful · 2026-04-28 03:26:04 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #70,998,973 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x317f6232…8a4c
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2bf9e449…5c20
0x065c9d…c394
4 touches
1 conflict
0x93e15703…9be6
0x065c9d…c394
4 touches
1 conflict
0x8fb893e6…a352
0x065c9d…c394
4 touches
1 conflict
0x87cf4f5b…1bde
0x065c9d…c394
2 touches
1 conflict
0x1abfbf4b…4efd
0x065c9d…c394
2 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
1 conflict on slot 0x317f6232a4…048a4c
Audit this contract →
← previous block·next block →recent activity