pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,442,442
← previous block
next block →
recent activity
Analyzing
Block #74,442,442
13 transactions · 11 stateful · 2026-05-14 02:01:13 UTC
Parallelism
85
/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,442,442
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x1a945f9c
#5
0x98717539
#6
0x98717539
#7
0xed82b078
#8
0xed82b078
#9
0x6a052d61
#10
execOrders
#11
execOrders
· blocks 1
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x10911bbe…a2a4
0x065c9d…c394
2 touches
0 conflicts
0x113b3a26…4a92
0x065c9d…c394
2 touches
0 conflicts
0x5027c885…2d39
0x065c9d…c394
2 touches
0 conflicts
0xa8d0976a…1e6b
0x065c9d…c394
2 touches
0 conflicts
0x00d1f9f0…0211
0x1efe02…37d6
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
0x310a7246ab…012dcb
Audit this contract →
← previous block
·
next block →
recent activity