pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,285,959
← previous block
next block →
recent activity
Analyzing
Block #74,285,959
10 transactions · 7 stateful · 2026-05-13 08:39:52 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,285,959
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
0x6df9e92b
#4
setData
#5
0x4a81a3…cac2
#6
0x1c81ec…a282
#7
0xc790ae…77d5
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3383890f…3807
0x065c9d…c394
2 touches
0 conflicts
0x8561529c…53a8
0x065c9d…c394
2 touches
0 conflicts
0x9e503d2b…9a76
0x065c9d…c394
2 touches
0 conflicts
0xdbcffd49…4ea5
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:
Perpl
1 conflict on slot
0xa998841984…609f45
Audit this contract →
← previous block
·
next block →
recent activity