pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,370,676
7 transactions · 5 stateful · 2026-05-04 11:51:43 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,370,676 · 7 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x802cf6a0…cf4f
0x065c9d…c394
4 touches
1 conflict
0xa8b4ae43…5c52
0x065c9d…c394
4 touches
1 conflict
0x1e70d541…0c5b
0x065c9d…c394
3 touches
1 conflict
0x3bc1dc65…2e17
0x065c9d…c394
3 touches
1 conflict
0xecdde6d1…9dba
0x065c9d…c394
2 touches
0 conflicts
0xff9593c7…ed75
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity