pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,853,146
← previous block
next block →
recent activity
Analyzing
Block #101,853,146
12 transactions · 12 stateful · 2026-09-04 08:28:39 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
#101,853,146
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
· blocks 1
#4
updatePrices
#5
0x5acec890
#6
execOrders
#7
create
#8
execFwdPositionOpsV2
· blocks 1
#9
0x6a9a81af
#10
setData
#3
execOrders
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd713bab…a651
0x34b655…2a6f
4 touches
1 conflict
0xe2a204e3…b989
0x34b655…2a6f
4 touches
1 conflict
0xe61a3df2…f763
0x34b655…2a6f
4 touches
1 conflict
0xf36124ad…c08f
0x34b655…2a6f
4 touches
1 conflict
0xf6c9806e…98e2
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x29a58269…011a
0x34b655…2a6f
4 touches
1 conflict
0x5c7b5ec0…0764
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
0xfd713bab1a…98a651
Audit this contract →
← previous block
·
next block →
recent activity