pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,103,231
8 transactions · 6 stateful · 2026-05-17 03:37:16 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,103,231 · 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08c3d91c…0298
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x360a6eb1…376a
0x065c9d…c394
2 touches
0 conflicts
0x87eb8b4a…e84f
0x065c9d…c394
2 touches
0 conflicts
0xab500414…98c8
0x065c9d…c394
2 touches
0 conflicts
0xba38536d…2b7d
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 0x08c3d91c49…250298
Audit this contract →
← previous block·next block →recent activity