pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,359,280
10 transactions · 9 stateful · 2026-05-09 01:34:55 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,359,280 · 10 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
1w02w13w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0xa9287840…1e02
0x065c9d…c394
4 touches
1 conflict
0x8001c7e4…9277
0x065c9d…c394
3 touches
1 conflict
0x8c6960b5…31d5
0x065c9d…c394
2 touches
0 conflicts
0xae6e010b…1397
0x065c9d…c394
2 touches
0 conflicts
0xc927e871…363c
0x065c9d…c394
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity