pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,538,606
← previous block
next block →
recent activity
Analyzing
Block #74,538,606
10 transactions · 9 stateful · 2026-05-14 12:44:21 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,538,606
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
updateDataFeedsValuesPartial
#3
forward
#4
forward
#5
setData
#6
0x39435dac
#7
0x39435dac
· blocks 1
#9
modifyLiquidities
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6464996…3af9
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x9c11d943…f33a
0x0555e3…2b9c
2 touches
0 conflicts
0xdf0f329c…3a5f
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…000b
0x24b8be…7f9e
2 touches
0 conflicts
0x1952c598…df64
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:
Perpl
1 conflict on slot
0xa6464996a2…6f3af9
Audit this contract →
← previous block
·
next block →
recent activity