pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,079,319
← previous block
next block →
recent activity
Analyzing
Block #100,079,319
11 transactions · 10 stateful · 2026-08-29 03:39:40 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,079,319
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x13828455
#2
0x80419567
#3
0x6ad2e98b
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x5acec890
· blocks 1
#7
0x5acec890
#9
setData
#8
0x928e4afa
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x02373c43…3cb3
0x34b655…2a6f
2 touches
0 conflicts
0x62030a81…91be
0x34b655…2a6f
2 touches
0 conflicts
0x70ace55b…8c81
0x34b655…2a6f
2 touches
0 conflicts
0x77db4f67…df1b
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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:
Perpl
1 conflict on slot
0xe5bb3628b5…71e5f1
Audit this contract →
← previous block
·
next block →
recent activity