pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,915,218
9 transactions · 9 stateful · 2026-05-16 06:40:50 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,915,218 · 9 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
1w02w13w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x16582ecc…a3ae
0x065c9d…c394
3 touches
1 conflict
0x1228312a…32f6
0x065c9d…c394
2 touches
0 conflicts
0x18204dad…e416
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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 0x348fda08cf…fc7e96
Audit this contract →
← previous block·next block →recent activity