pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,484,725
← previous block
next block →
recent activity
Analyzing
Block #102,484,725
11 transactions · 11 stateful · 2026-09-06 13:48:13 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,484,725
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#3
updatePrices
#4
0xab083028
#5
0x59558d29
#6
transferWithAuthorization
#7
setData
#8
execOrders
· blocks 2
#2
execOrders
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfd713bab…a651
0x34b655…2a6f
4 touches
1 conflict
0x9e07bd31…cfe3
0x34b655…2a6f
4 touches
1 conflict
0xc52785b9…08f8
0x34b655…2a6f
4 touches
1 conflict
0xeb4304a5…dd06
0x34b655…2a6f
4 touches
1 conflict
0xf2513b81…c680
0x34b655…2a6f
4 touches
1 conflict
0x01315072…0e2d
0x34b655…2a6f
4 touches
1 conflict
0x02372d42…1871
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity