pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,349,856
← previous block
next block →
recent activity
Analyzing
Block #93,349,856
11 transactions · 10 stateful · 2026-08-05 12:42:43 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
#93,349,856
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x4d8dc985
#3
0x39435dac
· blocks 1
#5
0x5acec890
#6
updateDataFeedsValuesPartial
#7
0xd708c5d8
#8
0x6a73303b
#9
setData
#10
updatePriceFeeds
#4
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x675d1afd…afef
0x34b655…2a6f
4 touches
1 conflict
0xfc8ca511…7a27
0x34b655…2a6f
3 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x1e4cddcd…a8ca
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
2 touches
0 conflicts
0x36639c6b…4d00
0x34b655…2a6f
2 touches
0 conflicts
0x394b760c…3c4c
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
1 conflict on slot
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity