pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,742,067
17 transactions · 11 stateful · 2026-05-01 13:58:30 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,742,067 · 17 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
1w02w03w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b909973…4a05
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x04c1fda6…fb22
0x065c9d…c394
3 touches
1 conflict
0x38185113…d57e
0x065c9d…c394
3 touches
1 conflict
0xd74d5bed…5e7e
0x2a68ba…90c5
2 touches
0 conflicts
0x1a4b4152…0a08
0x33663b…4897
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 0x1b9099739f…764a05
Audit this contract →
← previous block·next block →recent activity