pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,772,314
19 transactions · 13 stateful · 2026-05-15 14:47:32 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,772,314 · 19 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
2w03w14w15w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0xc13dc765…3c79
0x065c9d…c394
3 touches
1 conflict
0x8720bc5e…cf09
0x754704…b603
3 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
3 touches
1 conflict
0x6b44e829…8a96
0xd32edf…ff58
3 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity