pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,062,091
← previous block
next block →
recent activity
Analyzing
Block #120,062,091
14 transactions · 14 stateful · 2026-11-07 02:35:09 UTC
Parallelism
86
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,062,091
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6450738f
· blocks 1
#3
0x6450738f
#4
0x59558d29
#5
0x35e534ea
#6
0x35e534ea
#7
0x5acec890
#8
0x80419567
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
executeBatch
#12
setData
#13
execOrders
#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
0x0acd01b6…91c2
0x264123…670e
4 touches
1 conflict
0x6e773a5f…f43d
0x264123…670e
4 touches
1 conflict
0xc2575a0e…ff00
0x8121ee…ee7a
4 touches
1 conflict
0xc2575a0e…ff66
0x8121ee…ee7a
4 touches
1 conflict
0x46a42d19…e000
0x8121ee…ee7a
4 touches
1 conflict
0x816d0352…a531
0xf10d7c…cf8a
4 touches
1 conflict
0x46a42d19…e001
0x8121ee…ee7a
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
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
0x0acd01b67c…3591c2
Audit this contract →
← previous block
·
next block →
recent activity