pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,093,444
← previous block
next block →
recent activity
Analyzing
Block #100,093,444
12 transactions · 12 stateful · 2026-08-29 04:50:47 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,093,444
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
setData
#8
execFwdPositionOpsV2
#9
0xed82b078
#10
commit
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07183925…5c95
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
2 touches
0 conflicts
0x50f2372e…df46
0x34b655…2a6f
2 touches
0 conflicts
0x545e527e…0eb0
0x34b655…2a6f
2 touches
0 conflicts
0x5f46663c…b4c2
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
0x07183925ac…415c95
Audit this contract →
← previous block
·
next block →
recent activity