pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,588,496
← previous block
next block →
recent activity
Analyzing
Block #74,588,496
12 transactions · 11 stateful · 2026-05-14 18:19:52 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,588,496
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a0612bf
#2
0x98717539
· blocks 1
#3
0x0c7abd22
#4
updateDataFeedsValuesPartial
#5
transfer
#6
setData
#7
0x39435dac
#8
0x39435dac
#9
0x39435dac
#11
0x39435dac
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6eba5e7f…4b52
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
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x2c6c48a9…ba4a
0x065c9d…c394
2 touches
0 conflicts
0x4b95c1a4…cbea
0x065c9d…c394
2 touches
0 conflicts
0x570a189b…0b1c
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
0x6eba5e7f6a…ac4b52
Audit this contract →
← previous block
·
next block →
recent activity