pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,063,706
← previous block
next block →
recent activity
Analyzing
Block #120,063,706
11 transactions · 10 stateful · 2026-11-07 02:43:17 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,063,706
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x6450738f
#4
updatePrices
#5
updatePrices
#6
0x13828455
#7
0x80419567
#8
setData
#9
0x785f5745
#10
execOrders
#2
0x0c7abd22
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
0x2bfee832…1100
0xbb180c…d24f
4 touches
1 conflict
0xc2575a0e…fac5
0xbb180c…d24f
4 touches
1 conflict
0x2bfee832…1101
0xbb180c…d24f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
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:
0xbb180c8b…54d24f
1 conflict on slot
0x2bfee832a9…d71100
Audit this contract →
← previous block
·
next block →
recent activity