pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,338,461
18 transactions · 11 stateful · 2026-05-08 23:16:28 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,338,461 · 18 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
2w06w07w110w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83007222…b2eb
0xd32edf…ff58
7 touches
6 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x15bb3821…6b74
0x188d58…ea8e
2 touches
0 conflicts
0x15bb3821…6b75
0x188d58…ea8e
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0003
0x5afd3e…7620
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: 0xd32edf66…9fff58
6 conflicts on slot 0x8300722279…89b2eb
Audit this contract →
← previous block·next block →recent activity