pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,744,083
10 transactions · 9 stateful · 2026-05-01 14:11:58 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,744,083 · 10 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
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fb3d204…82ab
0x065c9d…c394
4 touches
1 conflict
0x4a962296…cdcc
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2c26ea4d…0332
0x065c9d…c394
3 touches
1 conflict
0x96b0a9cb…fd36
0x065c9d…c394
3 touches
1 conflict
0x24556577…89f6
0x065c9d…c394
3 touches
1 conflict
0x629c649e…201a
0x065c9d…c394
3 touches
1 conflict
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 0x8fb3d20414…9f82ab
Audit this contract →
← previous block·next block →recent activity