pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,640,544
← previous block
next block →
recent activity
Analyzing
Block #102,640,544
11 transactions · 11 stateful · 2026-09-07 02:57:41 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,640,544
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#3
0xab083028
· blocks 1
#4
0xab083028
#5
updateDataFeedsValuesPartial
#7
0x5acec890
#8
0x59558d29
#9
setData
#6
0x5acec890
#10
0xc7068c7b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
6
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49299fcf…c552
0x34b655…2a6f
4 touches
1 conflict
0x5edabc41…4098
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb1166afa…349b
0x34b655…2a6f
4 touches
1 conflict
0xb575cf74…fbd5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x352c45ab…a8ee
0x851145…3f07
4 touches
1 conflict
0x413476a1…3e03
0x851145…3f07
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:
Perpl
1 conflict on slot
0x49299fcf8b…f1c552
Audit this contract →
← previous block
·
next block →
recent activity