pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#107,443,772
← previous block
next block →
recent activity
Analyzing
Block #107,443,772
12 transactions · 11 stateful · 2026-09-23 22:45:10 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#107,443,772
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xab083028
#4
0xab083028
#5
0x3e2e8792
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0xed82b078
#9
setData
#10
0x61d59c2d
#11
execOrders
#2
0x0c7abd22
#6
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc009105d…96f7
0x37db7f…ec7b
4 touches
1 conflict
0x8a35acfb…d1b0
0x37db7f…ec7b
4 touches
1 conflict
0xd85497ea…896d
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
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:
0x37db7fbf…3eec7b
1 conflict on slot
0xc009105db3…e996f7
Audit this contract →
← previous block
·
next block →
recent activity