pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,501,520
8 transactions · 8 stateful · 2026-05-09 17:21:31 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,501,520 · 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
1w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x41a37de6…d03a
0x065c9d…c394
4 touches
1 conflict
0x4f7617cc…9488
0x065c9d…c394
4 touches
1 conflict
0x9d51b440…39d6
0x065c9d…c394
3 touches
1 conflict
0xeb30e071…a559
0x065c9d…c394
3 touches
1 conflict
0x5985e0d1…9a93
0x065c9d…c394
3 touches
1 conflict
0x0d01d425…f40d
0x065c9d…c394
3 touches
1 conflict
0x4d87512b…897c
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: 0x2a68ba18…8e90c5
3 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity