pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,076,607
← previous block
next block →
recent activity
Analyzing
Block #120,076,607
9 transactions · 8 stateful · 2026-11-07 03:48:22 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,076,607
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6450738f
· blocks 1
#2
0x6450738f
#4
execOrders
#5
0x35e534ea
#6
forward
#7
setData
#8
0x0c7abd22
#3
0x6450738f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x738cd500…0c02
0x264123…670e
4 touches
1 conflict
0xe9b0f2f0…0a50
0x264123…670e
4 touches
1 conflict
0x46a42d19…e000
0x8121ee…ee7a
4 touches
1 conflict
0xc2575a0e…ff64
0x8121ee…ee7a
4 touches
1 conflict
0xeeaa40cb…9100
0x8121ee…ee7a
4 touches
1 conflict
0xeeaa40cb…9101
0x8121ee…ee7a
4 touches
1 conflict
0xeeaa40cb…9102
0x8121ee…ee7a
4 touches
1 conflict
0x816d0352…a531
0xf10d7c…cf8a
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:
0x264123a9…fa670e
1 conflict on slot
0x738cd500f7…130c02
Audit this contract →
← previous block
·
next block →
recent activity