pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,192,151
← previous block
next block →
recent activity
Analyzing
Block #99,192,151
21 transactions · 19 stateful · 2026-08-26 01:00:06 UTC
Parallelism
81
/100
Blocked
47
%
Avg conflicts / tx
0.48
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,192,151
· 21 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
setData
#2
updatePrices
#3
0xab083028
· blocks 3
#6
0xab083028
#10
execOrders
#11
handleOps
#12
execOrders
#13
updateDataFeedsValuesPartial
#14
0x59558d29
#15
execOrders
· blocks 1
#19
0x6a8e3b0e
#4
0x6ad2e98b
· blocks 2
#9
0x8263f5d9
#16
execFwdPositionOpsV2
· blocks 3
#5
0xab083028
· blocks 1
#8
0x8263f5d9
#17
execFwdPositionOpsV2
#18
execFwdPositionOpsV2
#20
execOrders
#7
0x8263f5d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
7
w3
8
w2
9
w1
15
w0
16
w1
17
w2
18
w2
20
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0x8649e48f…941c
0xc8689a…ee79
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x3ee5a302…f47b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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:
Kuru Exchange: MarginAccount
3 conflicts on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity