pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,109,668
← previous block
next block →
recent activity
Analyzing
Block #120,109,668
12 transactions · 12 stateful · 2026-11-07 06:34:58 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,109,668
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6450738f
#2
0x6450738f
· blocks 1
#4
execOrders
· blocks 1
#6
0x59558d29
#7
0x35e534ea
#8
0x5acec890
#9
0x5acec890
#10
setData
#11
metacall
#3
0x6450738f
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x816d0352…a531
0xf10d7c…cf8a
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x46a42d19…e000
0x8121ee…ee7a
4 touches
1 conflict
0xc2575a0e…ff66
0x8121ee…ee7a
4 touches
1 conflict
0x13c221ec…7c8b
0x264123…670e
2 touches
0 conflicts
0x2cdc6344…ef96
0x264123…670e
2 touches
0 conflicts
0x4fe92899…f263
0x264123…670e
2 touches
0 conflicts
0x738cd500…0c02
0x264123…670e
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:
0xf10d7cb0…49cf8a
1 conflict on slot
0x816d0352cb…daa531
Audit this contract →
← previous block
·
next block →
recent activity