pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,201,677
10 transactions · 9 stateful · 2026-05-08 08:06:32 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,201,677 · 10 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
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x03dcbd1d…5c32
0x065c9d…c394
4 touches
1 conflict
0xd17b6bdb…770d
0x065c9d…c394
4 touches
1 conflict
0x7f189cf6…afab
0x065c9d…c394
4 touches
1 conflict
0xa141dbce…b969
0x065c9d…c394
2 touches
0 conflicts
0xba247a6d…9d22
0x065c9d…c394
2 touches
0 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
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