pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,409,566
← previous block
next block →
recent activity
Analyzing
Block #74,409,566
10 transactions · 9 stateful · 2026-05-13 22:22:23 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,409,566
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x6c05cd2b
· blocks 1
#6
0x6a04fa17
#7
setData
#8
0x39435dac
#9
jMMeC
#4
0x6c05cd2b
· blocks 1
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x692a4122…76b8
0x350035…7777
4 touches
1 conflict
0x00000000…0000
0x116e7d…d8f1
4 touches
1 conflict
0x00000000…0002
0x116e7d…d8f1
4 touches
1 conflict
0x00000000…0003
0x116e7d…d8f1
4 touches
1 conflict
0xb4e825af…69e0
0x3bd359…433a
4 touches
1 conflict
0xb7143610…adc4
0x3bd359…433a
4 touches
1 conflict
0xfbe161dd…757b
0x3bd359…433a
4 touches
1 conflict
0x0fc41e7b…6831
0x98dc6e…8633
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:
0x35003555…c27777
1 conflict on slot
0x692a41226b…cd76b8
Audit this contract →
← previous block
·
next block →
recent activity