pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,525,332
10 transactions · 8 stateful · 2026-05-14 11:14:46 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,525,332 · 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
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x76d061d9…4992
0x065c9d…c394
2 touches
0 conflicts
0x7b30a7b2…a2d0
0x065c9d…c394
2 touches
0 conflicts
0x7ba5d047…7d17
0x065c9d…c394
2 touches
0 conflicts
0x9df6d06b…85e7
0x065c9d…c394
2 touches
0 conflicts
0xfe37be0f…4fa0
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 0x47b807a243…c53307
Audit this contract →
← previous block·next block →recent activity