pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,095,985
← previous block
next block →
recent activity
Analyzing
Block #101,095,985
12 transactions · 9 stateful · 2026-09-01 16:59:30 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,095,985
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
0x5acec890
· blocks 1
#5
0x4cb2db39
#6
0x59558d29
#7
execPerpOps
#8
setData
#10
0xed82b078
#11
execOrders
#4
0x5acec890
· blocks 1
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x0476d77b…a514
0x34b655…2a6f
2 touches
0 conflicts
0x1e168c8b…6945
0x34b655…2a6f
2 touches
0 conflicts
0x2285ffd3…961c
0x34b655…2a6f
2 touches
0 conflicts
0x30c5329c…711c
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
0x74e485b13a…f0d380
Audit this contract →
← previous block
·
next block →
recent activity