pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,558,141
← previous block
next block →
recent activity
Analyzing
Block #93,558,141
9 transactions · 8 stateful · 2026-08-06 06:09:51 UTC
Parallelism
56
/100
Blocked
38
%
Avg conflicts / tx
0.78
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,558,141
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execOrders
· blocks 1
#2
0x5acec890
· blocks 3
#3
updateDataFeedsValuesPartial
#6
batchUpdate
#8
setData
#4
execFwdPositionOps
· blocks 2
#5
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
5
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bbb44c2…6731
0x34b655…2a6f
8 touches
6 conflicts
0x42e917f7…ed8c
0x34b655…2a6f
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
6 conflicts on slot
0x8bbb44c2da…bd6731
Audit this contract →
← previous block
·
next block →
recent activity