pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,796,103
← previous block
next block →
recent activity
Analyzing
Block #94,796,103
9 transactions · 8 stateful · 2026-08-10 14:13:23 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,796,103
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#5
0x3f5c179b
#6
execFwdPositionOps
#7
setData
#8
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8743e1ba…8331
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01dc29d8…bcd2
0x34b655…2a6f
2 touches
0 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
2 touches
0 conflicts
0x1282d637…5ff4
0x34b655…2a6f
2 touches
0 conflicts
0x206186c0…5ba4
0x34b655…2a6f
2 touches
0 conflicts
0x2e1f5171…ad2d
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
0x8743e1bab8…0a8331
Audit this contract →
← previous block
·
next block →
recent activity