pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,313,246
← previous block
next block →
recent activity
Analyzing
Block #74,313,246
8 transactions · 6 stateful · 2026-05-13 11:41:29 UTC
Parallelism
50
/100
Blocked
50
%
Avg conflicts / tx
0.75
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,313,246
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x6df9e92b
· blocks 3
#5
updateDataFeedsValuesPartial
#6
0x6a0463e1
#7
setData
#2
0x6df9e92b
· blocks 2
#3
0x6df9e92b
· blocks 1
#4
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc740dd24…9801
0x3bd359…433a
8 touches
6 conflicts
0x44ad89ba…cf83
0x5df178…7777
8 touches
6 conflicts
0x73131ffc…b46c
0x5df178…7777
8 touches
6 conflicts
0x00000000…0000
0x2c492d…444e
8 touches
6 conflicts
0x00000000…0001
0x2c492d…444e
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
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:
0x3bd359c1…15433a
6 conflicts on slot
0xc740dd24c2…bf9801
Audit this contract →
← previous block
·
next block →
recent activity