pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,765,504
29 transactions · 20 stateful · 2026-05-15 14:01:54 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,765,504 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w38w410w511w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0x94bb8c55…c160
0xd32edf…ff58
5 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x78ae17f2…53be
0x000000…012a
2 touches
0 conflicts
0x00000000…0001
0x010592…1c83
2 touches
0 conflicts
0x00000000…0006
0x010592…1c83
2 touches
0 conflicts
0x664a5455…8f40
0x010592…1c83
2 touches
0 conflicts
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: 0xab35264b…1cfa38
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity