pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,644,282
← previous block
next block →
recent activity
Analyzing
Block #74,644,282
12 transactions · 10 stateful · 2026-05-15 00:32:32 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,644,282
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
#2
0x1a945f9c
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
updatePriceFeedsIfNecessary
#6
0x6df9e92b
· blocks 1
#8
0x6a066a17
#9
setData
#10
0x39435dac
#11
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
0x0cc9b2…7777
4 touches
1 conflict
0x99a3a7c1…1e2b
0x0cc9b2…7777
4 touches
1 conflict
0x00000000…0002
0x019883…2a9a
4 touches
1 conflict
0x00000000…0000
0x019883…2a9a
4 touches
1 conflict
0xa10c86f8…4b74
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x8f6558c7…f346
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:
MONI (MONI)
1 conflict on slot
0x44ad89ba62…49cf83
Audit this contract →
← previous block
·
next block →
recent activity