pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,963,864
8 transactions · 7 stateful · 2026-05-11 20:54:43 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,963,864 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x84808094…255f
0x065c9d…c394
4 touches
1 conflict
0xd119dfdc…b728
0x065c9d…c394
3 touches
1 conflict
0x0a41679e…41db
0x065c9d…c394
2 touches
0 conflicts
0x557a63ca…66e9
0x065c9d…c394
2 touches
0 conflicts
0x8fecf9dc…7ced
0x065c9d…c394
2 touches
0 conflicts
0xa9b45046…9324
0x065c9d…c394
2 touches
0 conflicts
0xc012bc53…b34d
0x065c9d…c394
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