pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,744,521
11 transactions · 9 stateful · 2026-05-10 20:28:54 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,744,521 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w18w09w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0x0ac31945…2c72
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xed57bddf…1abf
0xc8689a…ee79
4 touches
1 conflict
0xc5564f8e…f4bf
0x6c4bfa…a540
4 touches
1 conflict
0xf0f673fd…37a7
0x6c4bfa…a540
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xae69c125…2379
0x2a68ba…90c5
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 0x529acb6ad1…f0fcc6
Audit this contract →
← previous block·next block →recent activity