pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,324,453
13 transactions · 11 stateful · 2026-05-08 21:43:21 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,324,453 · 13 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
1w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d0dfe2c…3345
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x6589f0e9…f65f
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0xd7942651…0110
0x065c9d…c394
4 touches
1 conflict
0xe19bfb64…df57
0x065c9d…c394
4 touches
1 conflict
0xf51c7793…cff4
0x065c9d…c394
4 touches
1 conflict
0xd821ae10…fe17
0xc8689a…ee79
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: 0x2a68ba18…8e90c5
3 conflicts on slot 0x8d0dfe2c6c…173345
Audit this contract →
← previous block·next block →recent activity