pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,786,713
← previous block
next block →
recent activity
Analyzing
Block #100,786,713
24 transactions · 22 stateful · 2026-08-31 15:03:04 UTC
Parallelism
83
/100
Blocked
23
%
Avg conflicts / tx
0.38
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,786,713
· 24 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
execOrder
#4
0x0c7abd22
#5
0x5acec890
#6
0x5acec890
#7
0x5acec890
#8
0x59558d29
#9
0xb414539a
· blocks 3
#10
execOrders
#11
execOrders
#12
execPerpOps
#13
execPerpOps
#14
batchRequestPriceCallback
#15
execFwdPositionOpsV2
#17
execFwdPositionOpsV2
#20
setData
#21
execOrders
· blocks 2
#16
0x62be7533
· blocks 2
#22
execOrders
· blocks 1
#18
0xed82b078
· blocks 1
#23
execOrders
#19
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
16
w1
18
w2
19
w3
21
w0
22
w1
23
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x378d062b…938f
0x065c9d…c394
4 touches
1 conflict
0x0c0e9ca6…8439
0x065c9d…c394
3 touches
1 conflict
0x10abefc9…c9bc
0x34ae4d…3fc5
2 touches
0 conflicts
0x10d80fee…dbda
0x34ae4d…3fc5
2 touches
0 conflicts
0x40970e69…da50
0x34ae4d…3fc5
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:
Kuru Exchange: MarginAccount
6 conflicts on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity