pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,308,647
10 transactions · 6 stateful · 2026-05-13 11:10:55 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,308,647 · 10 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcebf01c1…fae1
0x065c9d…c394
3 touches
1 conflict
0x320e4295…8a57
0x065c9d…c394
3 touches
1 conflict
0x55e1f978…7ed7
0x065c9d…c394
2 touches
0 conflicts
0x69a24455…5c42
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
0x065c9d…c394
2 touches
0 conflicts
0xfd92731b…f9e9
0x065c9d…c394
2 touches
0 conflicts
0x00000000…000b
0x18d19f…aaa2
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: 0x065c9d28…a9c394
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity