pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,970,583
← previous block
next block →
recent activity
Analyzing
Block #101,970,583
11 transactions · 10 stateful · 2026-09-04 18:22:42 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,970,583
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
#2
0x5acec890
· blocks 2
#4
0x5acec890
#5
0x5acec890
#8
setData
#9
execOrders
#10
execOrders
#3
0x5acec890
· blocks 1
#7
execOrder
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w2
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb8288e3…7979
0x34b655…2a6f
4 touches
1 conflict
0xddd20e39…d524
0x34b655…2a6f
4 touches
1 conflict
0x6c34b38f…c9e0
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x174fbe56…acd2
0x34b655…2a6f
2 touches
0 conflicts
0x19a9a256…4ba4
0x34b655…2a6f
2 touches
0 conflicts
0x23361cbc…b058
0x34b655…2a6f
2 touches
0 conflicts
0x36918c55…8424
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
0xdb8288e38f…6f7979
Audit this contract →
← previous block
·
next block →
recent activity