pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,502,345
← previous block
next block →
recent activity
Analyzing
Block #93,502,345
9 transactions · 8 stateful · 2026-08-06 01:29:22 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,502,345
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
0x3f5c179b
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
execOrders
#8
0x59558d29
#2
execFwdPositionOps
#4
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1b58b33…874f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xe47f0750…4816
0x851145…3f07
4 touches
1 conflict
0x03aa8b26…118a
0x34b655…2a6f
2 touches
0 conflicts
0x2c0fe9aa…dad9
0x34b655…2a6f
2 touches
0 conflicts
0x2d781581…d688
0x34b655…2a6f
2 touches
0 conflicts
0x3b3e5f00…9a88
0x34b655…2a6f
2 touches
0 conflicts
0x437104d2…66a2
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
0xb1b58b3385…e4874f
Audit this contract →
← previous block
·
next block →
recent activity