pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,746,355
10 transactions · 10 stateful · 2026-05-01 14:27:07 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,746,355 · 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae1b5695…ba17
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1b158d53…546b
0x065c9d…c394
3 touches
1 conflict
0x51084bb4…66e1
0x065c9d…c394
3 touches
1 conflict
0x8ea4a183…8272
0x065c9d…c394
3 touches
1 conflict
0x75c5222a…8291
0x065c9d…c394
2 touches
0 conflicts
0x508387de…c644
0x2a68ba…90c5
2 touches
0 conflicts
0xd74d5bed…5e7e
0x2a68ba…90c5
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 0xae1b5695b1…61ba17
Audit this contract →
← previous block·next block →recent activity