pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,204,709
8 transactions · 8 stateful · 2026-05-08 08:26:42 UTC
Parallelism
50/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,204,709 · 8 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
3w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xbf7eb941…5468
0x065c9d…c394
4 touches
1 conflict
0x7f189cf6…afab
0x065c9d…c394
4 touches
1 conflict
0xcb5e889b…e5c6
0x065c9d…c394
3 touches
1 conflict
0xd6992105…b676
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001a
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity