pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,441,045
← previous block
next block →
recent activity
Analyzing
Block #74,441,045
12 transactions · 11 stateful · 2026-05-14 01:51:54 UTC
Parallelism
75
/100
Blocked
18
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,441,045
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
updateDataFeedsValuesPartial
#3
0x98717539
· blocks 2
#6
setData
#7
0x6a052b32
#8
0x39435dac
#9
0x39435dac
#10
0x39435dac
#11
0x39435dac
#4
0x98717539
· blocks 1
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x11cb770d…a0a3
0x34b655…2a6f
2 touches
0 conflicts
0x5ba932bd…1010
0x34b655…2a6f
2 touches
0 conflicts
0x5f450515…3bc4
0x34b655…2a6f
2 touches
0 conflicts
0x6832c062…bb4c
0x34b655…2a6f
2 touches
0 conflicts
0x83f3d320…fb59
0x34b655…2a6f
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
3 conflicts on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity