pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,744,418
19 transactions · 13 stateful · 2026-05-10 20:28:13 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,744,418 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w213w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ac31945…2c72
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x992a8dea…cc15
0xd32edf…ff58
3 touches
1 conflict
0x978c45bd…62b3
0x065c9d…c394
2 touches
0 conflicts
0xe51bf299…e95b
0x065c9d…c394
2 touches
0 conflicts
0x194f2c02…19e6
0x2a68ba…90c5
2 touches
0 conflicts
0xae69c125…2379
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
3 conflicts on slot 0x0ac3194537…8f2c72
Audit this contract →
← previous block·next block →recent activity