pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,760,015
6 transactions · 5 stateful · 2026-05-15 13:25:09 UTC
Parallelism
50/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,760,015 · 6 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x07b3e4f2…749e
0x065c9d…c394
2 touches
0 conflicts
0x25e48776…00b3
0x065c9d…c394
2 touches
0 conflicts
0x7e8dabed…a0cc
0x065c9d…c394
2 touches
0 conflicts
0xb447b7f3…26c8
0x065c9d…c394
2 touches
0 conflicts
0xe9992bd2…acf4
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity