pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,108,232
← previous block
next block →
recent activity
Analyzing
Block #120,108,232
16 transactions · 15 stateful · 2026-11-07 06:27:42 UTC
Parallelism
88
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,108,232
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
postPriceList
#2
0x0c7abd22
#3
0x6450738f
· blocks 1
#5
execOrders
#6
0x59558d29
· blocks 1
#8
0x35e534ea
#9
0x5acec890
#10
0x5acec890
#11
0xa96df62f
#12
execOrders
#13
publishPrice
#14
setData
#15
0x0c7abd22
#4
0x6450738f
#7
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x816d0352…a531
0xfa2075…314c
4 touches
1 conflict
0x00000000…0002
0x80c745…7210
4 touches
1 conflict
0x00000000…0014
0x80c745…7210
4 touches
1 conflict
0x00000000…0015
0x80c745…7210
4 touches
1 conflict
0x00000000…0016
0x80c745…7210
4 touches
1 conflict
0x00000000…0017
0x80c745…7210
4 touches
1 conflict
0x7550940d…eb00
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:
0xfa2075ea…2b314c
1 conflict on slot
0x816d0352cb…daa531
Audit this contract →
← previous block
·
next block →
recent activity