pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,065,318
13 transactions · 10 stateful · 2026-04-28 10:47:39 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #71,065,318 · 13 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
2w03w14w25w310w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x6b98598a…ff5c
0x065c9d…c394
4 touches
1 conflict
0xb5cead27…5cda
0x065c9d…c394
4 touches
1 conflict
0xe772c5e7…c785
0x065c9d…c394
4 touches
1 conflict
0xeae31683…b021
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0x8fd63a…536c
4 touches
1 conflict
0x00000000…0001
0x8fd63a…536c
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: 0x065c9d28…a9c394
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity