pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,683,695
8 transactions · 6 stateful · 2026-05-01 07:29:48 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,683,695 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb12d0fc4…94ba
0x065c9d…c394
4 touches
1 conflict
0xf1587095…3526
0x065c9d…c394
4 touches
1 conflict
0x9d205c29…bfc7
0x065c9d…c394
3 touches
1 conflict
0x92420b6f…e8c4
0xd32edf…ff58
3 touches
1 conflict
0xa57c67f7…fa15
0x065c9d…c394
3 touches
1 conflict
0x71e85d86…f31a
0x065c9d…c394
3 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
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