pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,063,761
← previous block
next block →
recent activity
Analyzing
Block #120,063,761
9 transactions · 8 stateful · 2026-11-07 02:43:34 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,063,761
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6450738f
· blocks 1
#3
0x59558d29
#5
0x35e534ea
#6
updateDataFeedsValuesPartial
#7
forward
#8
setData
#2
0x6450738f
· blocks 1
#4
0x35e534ea
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72ba2fdc…939f
0x264123…670e
4 touches
1 conflict
0x615499e1…b800
0xf884c7…b285
4 touches
1 conflict
0x615499e1…b801
0xf884c7…b285
4 touches
1 conflict
0x615499e1…b803
0xf884c7…b285
4 touches
1 conflict
0x7550940d…eb00
0xf884c7…b285
4 touches
1 conflict
0x53373f0f…979b
0x264123…670e
4 touches
1 conflict
0xc2575a0e…f805
0xf884c7…b285
4 touches
1 conflict
0xc2575a0e…f99b
0xf884c7…b285
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:
0x264123a9…fa670e
1 conflict on slot
0x72ba2fdcd3…de939f
Audit this contract →
← previous block
·
next block →
recent activity