pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,648,934
← previous block
next block →
recent activity
Analyzing
Block #74,648,934
11 transactions · 10 stateful · 2026-05-15 01:03:27 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,648,934
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xd53e7c84
#2
0x39435dac
#3
0xed82b078
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a067157
#8
setData
#9
0x39435dac
· blocks 1
#4
0xed82b078
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x930275d7…d864
0x000000…8ba3
2 touches
0 conflicts
0xb2746a0b…9287
0x000000…8ba3
2 touches
0 conflicts
0x00000000…0004
0x29d207…1705
2 touches
0 conflicts
0x8ee994de…02b2
0x29d207…1705
2 touches
0 conflicts
0xbb371eab…3efc
0x29d207…1705
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity