pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,358,945
16 transactions · 13 stateful · 2026-05-09 01:32:42 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,358,945 · 16 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
2w04w05w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x4180ceeb…acbc
0x065c9d…c394
2 touches
0 conflicts
0x77edca4a…18bd
0x065c9d…c394
2 touches
0 conflicts
0x7cdd1735…55a8
0x065c9d…c394
2 touches
0 conflicts
0xcbaf5368…c5d4
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity