pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,734,183
8 transactions · 7 stateful · 2026-05-15 10:32:29 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,734,183 · 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50091a77…08e0
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9b3b6158…e113
0x065c9d…c394
3 touches
1 conflict
0xaa47ae8f…08ea
0x065c9d…c394
3 touches
1 conflict
0x6662f050…d4d3
0x065c9d…c394
2 touches
0 conflicts
0x811d8e88…8ae8
0x065c9d…c394
2 touches
0 conflicts
0x8de56389…b562
0x065c9d…c394
2 touches
0 conflicts
0x960cae19…8664
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 0x50091a77d7…5208e0
Audit this contract →
← previous block·next block →recent activity