pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,758,845
← previous block
next block →
recent activity
Analyzing
Block #74,758,845
7 transactions · 7 stateful · 2026-05-15 13:17:17 UTC
Parallelism
57
/100
Blocked
29
%
Avg conflicts / tx
0.29
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,758,845
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
allocate
· blocks 1
#3
updateDataFeedsValuesPartial
#5
setData
#6
0x39435dac
#2
0x0c7abd22
· blocks 1
#4
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x31b60059…7900
0x002560…1a4f
2 touches
0 conflicts
0x40ac22bb…a49b
0x002560…1a4f
2 touches
0 conflicts
0xe74d8286…be05
0x002560…1a4f
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x00000000…000d
0x1b6862…e19c
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:
0x1b68626d…2de19c
1 conflict on slot
0x0000000000…00001a
Audit this contract →
← previous block
·
next block →
recent activity