pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,183,286
← previous block
next block →
recent activity
Analyzing
Block #74,183,286
11 transactions · 8 stateful · 2026-05-12 21:17:13 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,183,286
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
supply
#2
0x1094dc9f
#3
0x0c7abd22
· blocks 1
#4
0xed82b078
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x62be7533
#9
0x6a039951
#10
setData
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabd592b5…80cf
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x62e20208…be65
0x0555e3…2b9c
2 touches
0 conflicts
0x8e80434a…a96d
0x0555e3…2b9c
2 touches
0 conflicts
0x97b2649e…0b22
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x094452…0a09
2 touches
0 conflicts
0x00000000…0003
0x094452…0a09
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:
0xd32edf66…9fff58
1 conflict on slot
0xabd592b53a…2480cf
Audit this contract →
← previous block
·
next block →
recent activity