pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,063,673
← previous block
next block →
recent activity
Analyzing
Block #120,063,673
12 transactions · 8 stateful · 2026-11-07 02:43:07 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,063,673
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x469a4c31
#2
0x469a4c31
· blocks 1
#4
0x59558d29
#5
0x59558d29
#6
0x35e534ea
#7
0xa96df62f
#8
0x80419567
#9
updatePrices
#10
setData
#11
0x0c7abd22
#3
0x469a4c31
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62d2faa4…8203
0xbb180c…d24f
4 touches
1 conflict
0xc2575a0e…fac4
0xbb180c…d24f
4 touches
1 conflict
0x292f70e5…9943
0x264123…670e
4 touches
1 conflict
0x62d2faa4…8200
0xbb180c…d24f
4 touches
1 conflict
0x62d2faa4…8201
0xbb180c…d24f
4 touches
1 conflict
0x3f855f1e…9ca4
0x264123…670e
2 touches
0 conflicts
0x5c76552f…4b64
0x264123…670e
2 touches
0 conflicts
0x5ee3f950…32bf
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:
0xbb180c8b…54d24f
1 conflict on slot
0x62d2faa44f…e58203
Audit this contract →
← previous block
·
next block →
recent activity