pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,056,499
← previous block
next block →
recent activity
Analyzing
Block #120,056,499
9 transactions · 9 stateful · 2026-11-07 02:06:54 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,056,499
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6450738f
#2
0x6450738f
#3
0x6450738f
· blocks 1
#5
0x59558d29
#6
execFwdPositionOpsV2
#7
0x57368ddf
#8
execFwdPositionOpsV2
#4
0x6450738f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x873b5142…bc81
0x9d2963…5798
4 touches
1 conflict
0x873b5142…bc82
0x9d2963…5798
4 touches
1 conflict
0xc2575a0e…04f9
0x9d2963…5798
4 touches
1 conflict
0x816d0352…a531
0xacb3f8…7f56
4 touches
1 conflict
0x316b8c52…15fa
0x264123…670e
4 touches
1 conflict
0xc41e22f7…ec34
0x264123…670e
4 touches
1 conflict
0x0b1da912…f800
0x9d2963…5798
4 touches
1 conflict
0x873b5142…bc80
0x9d2963…5798
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:
0x9d29630a…f15798
1 conflict on slot
0x873b51420e…77bc81
Audit this contract →
← previous block
·
next block →
recent activity