pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,651,980
20 transactions · 14 stateful · 2026-05-10 10:04:29 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,651,980 · 20 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
1w03w04w18w09w113w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb159af88…a9e7
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x7f81fb82…633e
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x7c6de558…768b
0x065c9d…c394
3 touches
1 conflict
0xc99c4504…f9a6
0xd32edf…ff58
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: 0x065c9d28…a9c394
3 conflicts on slot 0xb159af880b…47a9e7
Audit this contract →
← previous block·next block →recent activity