pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,510,439
← previous block
next block →
recent activity
Analyzing
Block #74,510,439
8 transactions · 7 stateful · 2026-05-14 09:34:25 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,510,439
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x785f5745
· blocks 1
#4
0x6a059798
#5
setData
#6
0x34653439
#7
0x39435dac
#3
0x785f5745
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…0000
0xbab229…9388
4 touches
1 conflict
0x00000000…0001
0xbab229…9388
4 touches
1 conflict
0x5860c4f3…0c39
0x3bd359…433a
4 touches
1 conflict
0x490911cc…5fea
0x0c65a0…0852
4 touches
1 conflict
0xaf11858f…8846
0x0c65a0…0852
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xd895ee0b…d301
0x34b655…2a6f
2 touches
0 conflicts
0xfa2527aa…9dd5
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:
0xbab2296c…069388
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity