pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,020,036
← previous block
next block →
recent activity
Analyzing
Block #101,020,036
13 transactions · 12 stateful · 2026-09-01 10:37:04 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,020,036
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
· blocks 1
#3
0x5acec890
#4
0x5acec890
#5
0x59558d29
#6
execOrders
#7
setData
#9
updatePosition
#10
relay
#11
0x6a96ab48
#12
execOrders
#8
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa59e109d…d53b
0x851145…3f07
4 touches
1 conflict
0xd840c9df…2d85
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1a79e9de…99e6
0x851145…3f07
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x08d53462…97ef
0x34ae4d…3fc5
2 touches
0 conflicts
0x5a409e7f…09b6
0x34ae4d…3fc5
2 touches
0 conflicts
0x7a12283f…b18a
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:
0x851145ea…9f3f07
1 conflict on slot
0xa59e109df5…34d53b
Audit this contract →
← previous block
·
next block →
recent activity