pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,216,190
← previous block
next block →
recent activity
Analyzing
Block #74,216,190
10 transactions · 8 stateful · 2026-05-13 00:56:02 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,216,190
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0x6a03cc9a
#4
exactOutputSingle
#5
updateDataFeedsValuesPartial
#7
setMerkleRoot
#8
setData
#9
jMMeC
#2
0x0c7abd22
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2e472ec6…2165
0xd32edf…ff58
3 touches
1 conflict
0x2a354a63…0515
0x065c9d…c394
2 touches
0 conflicts
0x78b2bfff…05b6
0x065c9d…c394
2 touches
0 conflicts
0xb75303c0…ec3c
0x065c9d…c394
2 touches
0 conflicts
0xb81bc2c3…f9f3
0x065c9d…c394
2 touches
0 conflicts
0xcf3283ba…c9fa
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:
0x065c9d28…a9c394
1 conflict on slot
0xf823e97fa0…262ee6
Audit this contract →
← previous block
·
next block →
recent activity