pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,338,192
10 transactions · 9 stateful · 2026-05-08 23:14:41 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,338,192 · 10 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
1w02w03w16w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x1decd3e9…dd8f
0x065c9d…c394
3 touches
1 conflict
0xbdff944d…447e
0x2a68ba…90c5
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x0fc41e7b…6831
0x98dc6e…8633
2 touches
0 conflicts
0x5b571ba0…f13a
0x98dc6e…8633
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 0xbd7e37a9b5…859eb5
Audit this contract →
← previous block·next block →recent activity