pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,549,888
← previous block
next block →
recent activity
Analyzing
Block #93,549,888
11 transactions · 10 stateful · 2026-08-06 05:28:22 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,549,888
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x928e4afa
#2
forward
#3
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
forward
#7
0x6a741bed
#8
setData
#9
0x36326531
#10
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388114fc…db6d
0x34b655…2a6f
4 touches
1 conflict
0x388114fc…db6c
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x02693e83…54be
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xaa185e92…f36e
0x34b655…2a6f
3 touches
1 conflict
0x6bab0076…422b
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
0x388114fca1…98db6d
Audit this contract →
← previous block
·
next block →
recent activity