pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,482,793
11 transactions · 10 stateful · 2026-05-09 15:16:48 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,482,793 · 11 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
2w04w15w16w27w38w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x95cde0c5…2bbf
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe9d41178…8804
0x065c9d…c394
4 touches
1 conflict
0xd93115d7…278b
0x065c9d…c394
4 touches
1 conflict
0x61d7a1e5…7622
0x065c9d…c394
3 touches
1 conflict
0x32daed04…92c1
0x065c9d…c394
3 touches
1 conflict
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