pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,050,078
← previous block
next block →
recent activity
Analyzing
Block #120,050,078
12 transactions · 10 stateful · 2026-11-07 01:34:27 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,050,078
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6450738f
· blocks 1
#3
0x6450738f
#4
execOrders
#5
0x35e534ea
#6
0x5acec890
#7
updatePrices
#8
artefact_keep
#9
execOrders
#10
setData
#11
0x0c7abd22
#2
0x6450738f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7550940d…eb00
0xf884c7…b285
4 touches
1 conflict
0x9a2a3d9d…729e
0x264123…670e
4 touches
1 conflict
0xbb192ad7…8085
0x264123…670e
4 touches
1 conflict
0xc2575a0e…f99b
0xf884c7…b285
4 touches
1 conflict
0xecfd95d3…4b80
0xf884c7…b285
4 touches
1 conflict
0xecfd95d3…4b81
0xf884c7…b285
4 touches
1 conflict
0xecfd95d3…4b82
0xf884c7…b285
4 touches
1 conflict
0x816d0352…a531
0xfa2075…314c
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:
0xf884c763…b5b285
1 conflict on slot
0x7550940df1…2beb00
Audit this contract →
← previous block
·
next block →
recent activity