pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,484,215
← previous block
next block →
recent activity
Analyzing
Block #74,484,215
10 transactions · 9 stateful · 2026-05-14 06:39:11 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,484,215
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
setData
#5
forward
#6
0x6df9e92b
· blocks 1
#8
0x39435dac
· blocks 1
#7
0x6df9e92b
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
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
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x7cee1be1…e770
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0xcc67aa…c71c
4 touches
1 conflict
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
1 conflict on slot
0x00c46468d1…54f328
Audit this contract →
← previous block
·
next block →
recent activity