pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,470,519
← previous block
next block →
recent activity
Analyzing
Block #74,470,519
10 transactions · 6 stateful · 2026-05-14 05:08:01 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,470,519
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x323fe4ce
#5
0x6df9e92b
· blocks 1
#7
0xb36b0c…cde2
#8
0x214928…0426
#9
setData
#6
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xcc67aa…c71c
4 touches
1 conflict
0x00c46468…f328
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x44ad89ba…cf83
0x5c2513…7777
4 touches
1 conflict
0xce2b6650…ecc3
0x5c2513…7777
4 touches
1 conflict
0x00000000…0000
0xcc67aa…c71c
4 touches
1 conflict
0x4f900fbe…7a81
0x065c9d…c394
2 touches
0 conflicts
0xa8d0976a…1e6b
0x065c9d…c394
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:
0xcc67aab1…cac71c
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity