pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#103,211,114
← previous block
next block →
recent activity
Analyzing
Block #103,211,114
13 transactions · 12 stateful · 2026-09-09 02:54:07 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#103,211,114
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0xab083028
#3
0x8263f5d9
#4
updatePrices
#5
0x3e2e8792
· blocks 1
#6
0x5acec890
#8
0x5acec890
#9
0x5acec890
#10
0x59558d29
#11
setData
#12
execOrders
#7
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0265568b…f643
0x34b655…2a6f
2 touches
0 conflicts
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x172cd750…1d94
0x34b655…2a6f
2 touches
0 conflicts
0x18cf84a6…09e4
0x34b655…2a6f
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity