pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,300,825
← previous block
next block →
recent activity
Analyzing
Block #74,300,825
10 transactions · 8 stateful · 2026-05-13 10:18:52 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,300,825
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
#2
addLiquidity
#3
updateDataFeedsValuesPartial
#4
0x785f5745
#5
0x32f78d…7ce3
#6
0x6a045084
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1c247f42…91b5
0x065c9d…c394
2 touches
0 conflicts
0x258618a6…bf85
0x065c9d…c394
2 touches
0 conflicts
0x3cfbee5f…363f
0x065c9d…c394
2 touches
0 conflicts
0x59d6c587…a52d
0x065c9d…c394
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:
Perpl
1 conflict on slot
0x0eac637818…cb36f4
Audit this contract →
← previous block
·
next block →
recent activity