pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,986,526
← previous block
next block →
recent activity
Analyzing
Block #101,986,526
13 transactions · 13 stateful · 2026-09-04 19:43:35 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,986,526
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
0x59558d29
#4
collect
#5
setData
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
#8
buy
#10
forward
#11
forward
#12
execOrders
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31f6e455…1aca
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0xb37dfb6b…268f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd5982776…4847
0x34b655…2a6f
4 touches
1 conflict
0x24b08f9c…e594
0x34b655…2a6f
4 touches
1 conflict
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
0x31f6e455f3…4f1aca
Audit this contract →
← previous block
·
next block →
recent activity