pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,400,155
← previous block
next block →
recent activity
Analyzing
Block #74,400,155
9 transactions · 7 stateful · 2026-05-13 21:19:42 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,400,155
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
get_block_hash_257335279069929
#3
0x1a945f9c
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x6df9e92b
· blocks 1
#8
0x39435dac
#7
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0x5df178…7777
4 touches
1 conflict
0x73131ffc…b46c
0x5df178…7777
4 touches
1 conflict
0x00000000…0000
0x2c492d…444e
4 touches
1 conflict
0x00000000…0001
0x2c492d…444e
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xc740dd24…9801
0x3bd359…433a
4 touches
1 conflict
0x32aaa126…37ba
0x1efe02…37d6
2 touches
0 conflicts
0x560b9bed…8e7a
0x1efe02…37d6
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:
0x5df178c7…167777
1 conflict on slot
0x44ad89ba62…49cf83
Audit this contract →
← previous block
·
next block →
recent activity