pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,261,308
20 transactions · 15 stateful · 2026-05-08 14:43:03 UTC
Parallelism
90/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,261,308 · 20 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
6w010w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x048a92f2…4044
0x96b79e…d00a
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0a2250a8…3cb1
0x34b655…2a6f
2 touches
0 conflicts
0x0f41c833…9c38
0x34b655…2a6f
2 touches
0 conflicts
0x388e001a…7e04
0x34b655…2a6f
2 touches
0 conflicts
0x47c1a8e8…f74a
0x34b655…2a6f
2 touches
0 conflicts
0x693d979a…f2bd
0x34b655…2a6f
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: 0x96b79ef4…d2d00a
1 conflict on slot 0x048a92f283…4b4044
Audit this contract →
← previous block·next block →recent activity