pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,696,530
11 transactions · 10 stateful · 2026-05-01 08:55:18 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,696,530 · 11 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
2w04w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe3d37ee…6e67
0x34b655…2a6f
4 touches
1 conflict
0x3e4b02f8…bf0d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbc04d98e…a484
0x34b655…2a6f
4 touches
1 conflict
0xcbd23469…a4df
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfadc118d…5d64
0x34b655…2a6f
4 touches
1 conflict
0x60c05a72…6ade
0x065c9d…c394
3 touches
1 conflict
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: 0x34b6552d…112a6f
1 conflict on slot 0xfe3d37ee7e…836e67
Audit this contract →
← previous block·next block →recent activity