pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,063,732
← previous block
next block →
recent activity
Analyzing
Block #120,063,732
9 transactions · 8 stateful · 2026-11-07 02:43:25 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,063,732
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6450738f
· blocks 1
#3
execOrders
#4
0x35e534ea
#5
0x35e534ea
#6
0x35e534ea
#7
updateDataFeedsValuesPartial
#8
0x5acec890
#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
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
0x72ba2fdc…939f
0x264123…670e
4 touches
1 conflict
0xc2575a0e…f99b
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
0x615499e1dd…f8b800
Audit this contract →
← previous block
·
next block →
recent activity