pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,388,177
← previous block
next block →
recent activity
Analyzing
Block #93,388,177
13 transactions · 10 stateful · 2026-08-05 15:55:25 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,388,177
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6e060c2c
#2
0x05ee6a22
#3
0x4d8dc985
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
batchCancelOrders
#7
0x0f6795d9
· blocks 1
#9
0x0f6795d9
#10
setData
#11
0x59558d29
#12
0xc7e3ec2c
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x2b4de119…038c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0036
0x39f901…6bdf
2 touches
0 conflicts
0xc5819118…1448
0x39f901…6bdf
2 touches
0 conflicts
0x6237f1a7…2f59
0x3bd359…433a
2 touches
0 conflicts
0xbfe7fd3a…3168
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x47bae1…7568
2 touches
0 conflicts
0x00000000…0003
0x47bae1…7568
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
0x1d351a9b20…2df2dd
Audit this contract →
← previous block
·
next block →
recent activity