pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,387,360
← previous block
next block →
recent activity
Analyzing
Block #120,387,360
10 transactions · 9 stateful · 2026-11-08 05:56:33 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,387,360
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setData
#2
0x6450738f
· blocks 1
#4
0x6450738f
#5
execOrders
#6
0x35e534ea
#7
0x35e534ea
#8
0x0c7abd22
#9
0x5acec890
#3
0x6450738f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2575a0e…0fcd
0xae8e0c…e422
4 touches
1 conflict
0x08da1be4…1f02
0xae8e0c…e422
4 touches
1 conflict
0x66322cb4…dd80
0xae8e0c…e422
4 touches
1 conflict
0x66322cb4…dd81
0xae8e0c…e422
4 touches
1 conflict
0x66322cb4…dd82
0xae8e0c…e422
4 touches
1 conflict
0x69db23d3…ca80
0xae8e0c…e422
4 touches
1 conflict
0xc2575a0e…0f80
0xae8e0c…e422
4 touches
1 conflict
0x157d0d1d…3df2
0x264123…670e
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:
0xae8e0cf4…09e422
1 conflict on slot
0xc2575a0e9e…720fcd
Audit this contract →
← previous block
·
next block →
recent activity