pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,555,974
← previous block
next block →
recent activity
Analyzing
Block #93,555,974
13 transactions · 11 stateful · 2026-08-06 05:58:57 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
#93,555,974
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xc0ea4b44
#3
0xeb282f7f
#4
0x928e4afa
#5
0x3f5c179b
#6
0x3f5c179b
#7
batchUpdate
#8
0x0f6795d9
#9
0x0f6795d9
· blocks 1
#11
updateDataFeedsValuesPartial
#12
setData
#10
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69a45f39…39aa
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa67b76d8…97ff
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0008
0x2d18aa…338c
2 touches
0 conflicts
0x00000000…0009
0x2d18aa…338c
2 touches
0 conflicts
0x00000000…000a
0x2d18aa…338c
2 touches
0 conflicts
0xf0434fb0…47e0
0x3bd359…433a
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
0x69a45f39d6…c739aa
Audit this contract →
← previous block
·
next block →
recent activity