pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,063,748
← previous block
next block →
recent activity
Analyzing
Block #120,063,748
12 transactions · 12 stateful · 2026-11-07 02:43:30 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,063,748
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x6450738f
#4
0x6450738f
· blocks 2
#7
0x59558d29
#8
forward
#9
execFwdPositionOpsV2
#10
setData
#11
execOrders
#2
0x0c7abd22
#5
0x469a4c31
· blocks 1
#6
0x6450738f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x816d0352…a531
0x8d61bb…7a08
6 touches
3 conflicts
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
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0055
0x1b6862…e19c
4 touches
1 conflict
0x063eca74…c2e2
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:
0x8d61bbb3…b37a08
3 conflicts on slot
0x816d0352cb…daa531
Audit this contract →
← previous block
·
next block →
recent activity