pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,464,417
← previous block
next block →
recent activity
Analyzing
Block #74,464,417
12 transactions · 7 stateful · 2026-05-14 04:27:29 UTC
Parallelism
83
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,464,417
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
dagSwapByOrderId
#2
updatePrices
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x39435dac
#6
transfer
#7
0x1fef69…5c3f
#8
0x6eb740…9a01
#9
0x9c51c4…0df0
#10
0xabc5bb…181a
#11
setData
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2732e692…6bb6
0x000000…012a
2 touches
0 conflicts
0x4d8766fd…f1c6
0x000000…012a
2 touches
0 conflicts
0x78eb0de5…1db2
0x01bff4…1071
2 touches
0 conflicts
0x7d96cf5d…df0f
0x01bff4…1071
2 touches
0 conflicts
0x00000000…0002
0x942644…91ab
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:
0xab35264b…1cfa38
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity