pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,063,768
← previous block
next block →
recent activity
Analyzing
Block #120,063,768
13 transactions · 12 stateful · 2026-11-07 02:43:36 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,063,768
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6450738f
#3
0x6450738f
· blocks 1
#5
0x59558d29
· blocks 1
#7
execOrders
#8
execOrders
#9
executeBatch
#10
execOrders
#11
execFwdPositionOpsV2
#12
execFwdPositionOpsV2
#4
0x6450738f
#6
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc52e52b2…c504
0xf3fb2e…41eb
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
0x31ab7183…c600
0xf3fb2e…41eb
4 touches
1 conflict
0xc2575a0e…f914
0xf3fb2e…41eb
4 touches
1 conflict
0xc52e52b2…c500
0xf3fb2e…41eb
4 touches
1 conflict
0xc52e52b2…c501
0xf3fb2e…41eb
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:
0xf3fb2ec6…7d41eb
1 conflict on slot
0xc52e52b2c3…5bc504
Audit this contract →
← previous block
·
next block →
recent activity