pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,017,187
← previous block
next block →
recent activity
Analyzing
Block #101,017,187
12 transactions · 11 stateful · 2026-09-01 10:22:44 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,017,187
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
· blocks 1
#4
0x5acec890
#5
0x5acec890
#6
0x5acec890
#7
0x5acec890
· blocks 1
#8
0x59558d29
#9
setData
#11
0x6a96a7ec
#3
execOrders
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f2778a8…8415
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x07b538eb…09f8
0x34b655…2a6f
2 touches
0 conflicts
0x0a809ce1…7894
0x34b655…2a6f
2 touches
0 conflicts
0x5fe611e7…87aa
0x34b655…2a6f
2 touches
0 conflicts
0x74a8e861…0343
0x34b655…2a6f
2 touches
0 conflicts
0x7d6b9af1…9a38
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
0x4f2778a84d…738415
Audit this contract →
← previous block
·
next block →
recent activity