pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,467,598
← previous block
next block →
recent activity
Analyzing
Block #93,467,598
8 transactions · 7 stateful · 2026-08-05 22:34:42 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,467,598
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
#2
execFwdPositionOps
· blocks 2
#3
updateDataFeedsValuesPartial
#5
0x6a73bafa
#6
setData
#4
execFwdPositionOps
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x861e5aef…d32c
0x34b655…2a6f
6 touches
3 conflicts
0x5110a94f…86d1
0x34b655…2a6f
4 touches
1 conflict
0x5110a94f…86d2
0x34b655…2a6f
4 touches
1 conflict
0xf2f960b1…84b5
0x34b655…2a6f
4 touches
1 conflict
0x00a85cec…573e
0x34b655…2a6f
2 touches
0 conflicts
0x0110331c…b891
0x34b655…2a6f
2 touches
0 conflicts
0x085783c4…ec4d
0x34b655…2a6f
2 touches
0 conflicts
0x0a681e3c…1316
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
3 conflicts on slot
0x861e5aeffa…5cd32c
Audit this contract →
← previous block
·
next block →
recent activity