pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,466,577
← previous block
next block →
recent activity
Analyzing
Block #74,466,577
12 transactions · 7 stateful · 2026-05-14 04:41:53 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,466,577
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x6df9e92b
· blocks 2
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x04e0db…d50a
#8
0x20a60d…717d
#9
0x45e1c5…705e
#10
0x557bb3…ca9a
#11
0x39435dac
#3
0x6df9e92b
· blocks 1
#4
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x44ad89ba…cf83
0x5c2513…7777
6 touches
3 conflicts
0xce2b6650…ecc3
0x5c2513…7777
6 touches
3 conflicts
0x00c46468…f328
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0xcc67aa…c71c
6 touches
3 conflicts
0x00000000…0001
0xcc67aa…c71c
6 touches
3 conflicts
0x85a88798…f85e
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
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
3 conflicts on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity