pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,201,865
← previous block
next block →
recent activity
Analyzing
Block #73,201,865
9 transactions · 8 stateful · 2026-05-08 08:07:47 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,201,865
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
#2
updatePrices
· blocks 1
#4
0x39435dac
· blocks 1
#6
0x69fd9a4b
#7
updateDataFeedsValuesPartial
#8
setData
#3
updatePrices
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x21d22421…0b7a
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x3b8ffd61…f3ad
0x34b655…2a6f
4 touches
1 conflict
0x62ca9ce0…edb3
0x34b655…2a6f
4 touches
1 conflict
0xe917d327…ad61
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
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:
0xab35264b…1cfa38
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity