pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,287,379
← previous block
next block →
recent activity
Analyzing
Block #92,287,379
11 transactions · 10 stateful · 2026-08-01 19:36:15 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,287,379
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a6e4b27
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
0x39435dac
#6
0x0f6795d9
#7
setData
#8
updatePrices
#9
0x59558d29
#10
0xc7e3ec2c
#2
0x6a6e4b27
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0490581d…adaf
0x34b655…2a6f
2 touches
0 conflicts
0x0b7094d9…4373
0x34b655…2a6f
2 touches
0 conflicts
0x0dd7d6d8…3700
0x34b655…2a6f
2 touches
0 conflicts
0x0fe1e6e0…f553
0x34b655…2a6f
2 touches
0 conflicts
0x1088dfef…9fc2
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity