pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,667,311
← previous block
next block →
recent activity
Analyzing
Block #74,667,311
12 transactions · 10 stateful · 2026-05-15 03:06:20 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,667,311
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x785f5745
#5
forward
#6
0x6df9e92b
· blocks 1
#8
0x6a068e23
#9
setData
#10
0x3e3e5f…9758
#11
0xa0d317…d371
#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
0x81a7ba4d…8c4b
0x23c26b…7777
4 touches
1 conflict
0x08fdca0b…4abf
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x44ad89ba…cf83
0x23c26b…7777
4 touches
1 conflict
0x00000000…0000
0xfdc9ea…8789
4 touches
1 conflict
0x00000000…0002
0xfdc9ea…8789
4 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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:
Mouch (MOUCH)
1 conflict on slot
0x81a7ba4dd6…568c4b
Audit this contract →
← previous block
·
next block →
recent activity