pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,319,423
← previous block
next block →
recent activity
Analyzing
Block #74,319,423
14 transactions · 12 stateful · 2026-05-13 12:22:36 UTC
Parallelism
86
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,319,423
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
commitVerification
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
multicall
#6
0x5bf9264c
· blocks 1
#8
0x1a945f9c
#9
updateDataFeedsValuesPartial
#10
setData
#11
0x6a046d84
#12
0x39435dac
· blocks 1
#7
0x5bf9264c
#13
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
12
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…000a
0x1b5fbe…500f
2 touches
0 conflicts
0x00000000…000b
0x1b5fbe…500f
2 touches
0 conflicts
0x1d10e771…bb26
0x3bd359…433a
2 touches
0 conflicts
0x49b12261…ad19
0x3bd359…433a
2 touches
0 conflicts
0xd73b6915…631f
0x3bd359…433a
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:
0x34b6552d…112a6f
1 conflict on slot
0xc824469a90…af641c
Audit this contract →
← previous block
·
next block →
recent activity