pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,898,593
← previous block
next block →
recent activity
Analyzing
Block #74,898,593
11 transactions · 8 stateful · 2026-05-16 04:49:58 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,898,593
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
#2
updatePrices
#3
0x5bf9264c
#4
0x5bf9264c
#5
0x1a945f9c
· blocks 1
#6
updateDataFeedsValuesPartial
#8
updateTemporalNumericValuesV1
#9
setData
#10
0x053c0052
#7
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f312413…2428
0x91b81b…6d56
4 touches
1 conflict
0x00bac013…a28c
0x91b81b…6d56
4 touches
1 conflict
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x493bc17c…2318
0x1efe02…37d6
2 touches
0 conflicts
0x50d8ade7…3fd4
0x1efe02…37d6
2 touches
0 conflicts
0xa67b76d8…97ff
0x1efe02…37d6
2 touches
0 conflicts
0xac2a0273…7212
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:
0x91b81bfb…8e6d56
1 conflict on slot
0x9f3124135b…9b2428
Audit this contract →
← previous block
·
next block →
recent activity