pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,273,732
10 transactions · 10 stateful · 2026-05-08 16:05:48 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,273,732 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1ae
0x8d66a4…3095
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x0335ae80…8414
0x8d66a4…3095
4 touches
1 conflict
0x31ba6c4c…e2a4
0x065c9d…c394
2 touches
0 conflicts
0xdca60185…288b
0x065c9d…c394
2 touches
0 conflicts
0xe4da7ec3…f318
0x065c9d…c394
2 touches
0 conflicts
0x8d0dfe2c…3345
0x2a68ba…90c5
2 touches
0 conflicts
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: 0x8d66a43f…113095
1 conflict on slot 0x8a35acfbc1…6bd1ae
Audit this contract →
← previous block·next block →recent activity