pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,338,727
18 transactions · 17 stateful · 2026-05-08 23:18:14 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,338,727 · 18 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
2w03w06w17w18w09w111w012w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xfdc9ea…8789
4 touches
1 conflict
0x08fdca0b…4abf
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x8a35acfb…d1ae
0x8d66a4…3095
4 touches
1 conflict
0x96504a63…52d2
0x8d66a4…3095
4 touches
1 conflict
0x00000000…0000
0xfdc9ea…8789
4 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: 0x065c9d28…a9c394
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity