pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,100,044
← previous block
next block →
recent activity
Analyzing
Block #106,100,044
9 transactions · 9 stateful · 2026-09-19 06:00:32 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,100,044
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x5acec890
#4
setData
#5
0x1ea3e879
· blocks 2
#8
execOrders
#6
0x1ea3e879
· blocks 1
#7
0x1ea3e879
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09a3c714…ea15
0x6f6493…b480
6 touches
3 conflicts
0x0f3b1965…7855
0x6f6493…b480
6 touches
3 conflicts
0x120312ce…abd0
0x6f6493…b480
6 touches
3 conflicts
0x16f7f665…9f0a
0x6f6493…b480
6 touches
3 conflicts
0x172fbcbb…95d0
0x6f6493…b480
6 touches
3 conflicts
0x241f7f86…2b02
0x6f6493…b480
6 touches
3 conflicts
0x2f3b754e…358b
0x6f6493…b480
6 touches
3 conflicts
0x3078545b…732b
0x6f6493…b480
6 touches
3 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:
0x6f6493e3…08b480
3 conflicts on slot
0x09a3c71476…72ea15
Audit this contract →
← previous block
·
next block →
recent activity