pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,648,300
9 transactions · 9 stateful · 2026-05-10 09:39:44 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,648,300 · 9 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
1w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb159af88…a9e7
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5d671884…bb39
0x065c9d…c394
2 touches
0 conflicts
0x6c123e52…1207
0x065c9d…c394
2 touches
0 conflicts
0x90f331dd…4f01
0x065c9d…c394
2 touches
0 conflicts
0xc2b6861c…2979
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
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 0xb159af880b…47a9e7
Audit this contract →
← previous block·next block →recent activity