pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,344,461
← previous block
next block →
recent activity
Analyzing
Block #74,344,461
8 transactions · 6 stateful · 2026-05-13 15:09:03 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,344,461
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x55e58ed0
#3
0x1a945f9c
#4
0x98717539
#5
0xe9316489
· blocks 1
#7
setData
#6
0xe9316489
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee133c62…8063
0x96b79e…d00a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0xf123b3fb…7bfb
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
2 touches
0 conflicts
0xdae29e50…7c09
0xaa3145…feec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
2 touches
0 conflicts
0x72ecfa6d…6793
0xea1b8e…c5ec
2 touches
0 conflicts
0x9c8d6dd6…d619
0xea1b8e…c5ec
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:
0x96b79ef4…d2d00a
1 conflict on slot
0xee133c62cf…b58063
Audit this contract →
← previous block
·
next block →
recent activity