pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,437,522
← previous block
next block →
recent activity
Analyzing
Block #102,437,522
12 transactions · 12 stateful · 2026-09-06 09:49:04 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,437,522
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
execute
#4
0x59558d29
· blocks 1
#6
execPerpOps
#7
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
#9
setData
#10
depositTo
#5
0x59558d29
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x077d58c3…8ed7
0x34b655…2a6f
2 touches
0 conflicts
0x16df2bbf…416a
0x34b655…2a6f
2 touches
0 conflicts
0x1e4cc7e7…b4d3
0x34b655…2a6f
2 touches
0 conflicts
0x25c70dfd…4544
0x34b655…2a6f
2 touches
0 conflicts
0x2a59096f…a8d6
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004c
Audit this contract →
← previous block
·
next block →
recent activity