pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,649,424
16 transactions · 11 stateful · 2026-05-10 09:47:19 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,649,424 · 16 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
2w06w07w110w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
4 touches
1 conflict
0xd49762c9…1359
0x34b655…2a6f
4 touches
1 conflict
0x462d8e25…1e49
0x34b655…2a6f
4 touches
1 conflict
0xb159af88…a9e7
0x065c9d…c394
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0xedb848fe…6534
0x34b655…2a6f
4 touches
1 conflict
0xba5743c7…21c2
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity