pev.One block, wave by wave
analyticsdocs
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,369,364
12 transactions · 9 stateful · 2026-05-13 17:54:40 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,369,364 · 12 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
1w09w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x3cf2fdf6…f98f
0x065c9d…c394
3 touches
1 conflict
0x0da53d80…5998
0x065c9d…c394
2 touches
0 conflicts
0x2eba889b…45e3
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x4ef6a331…13ec
0x065c9d…c394
2 touches
0 conflicts
0xf27badbf…8b5e
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