pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,200,778
11 transactions · 8 stateful · 2026-05-08 08:00:33 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,200,778 · 11 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
1w04w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x2a354a63…0515
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x7f9e6685…0809
0x065c9d…c394
2 touches
0 conflicts
0x82de79db…5547
0x065c9d…c394
2 touches
0 conflicts
0x89bcddb5…2af4
0x065c9d…c394
2 touches
0 conflicts
0x93cd481c…a02a
0x065c9d…c394
2 touches
0 conflicts
0xa16e2994…4f28
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
1 conflict on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity