pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,869,260
← previous block
next block →
recent activity
Analyzing
Block #73,869,260
15 transactions · 9 stateful · 2026-05-11 10:24:56 UTC
Parallelism
87
/100
Blocked
11
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,869,260
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa416bf…8e82
#2
0x24093e…93f7
#3
0xd58eb7…edff
#4
0x7856dd…b5c1
#5
0xa52c40…0d8f
#6
0x39435dac
#7
mint
· blocks 1
#8
0x000000b2
#9
forward
#10
updateDataFeedsValuesPartial
#11
setData
#13
0x6a01aeef
#14
0x785f5745
#12
mint
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x6b385104…3671
0x1414f3…5137
2 touches
0 conflicts
0x8054f4f0…25b1
0x1414f3…5137
2 touches
0 conflicts
0x00000000…000b
0x2a347b…e9d3
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x15d039e7…4bb6
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:
0x1414f3ba…045137
1 conflict on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity