pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,039,486
← previous block
next block →
recent activity
Analyzing
Block #102,039,486
12 transactions · 12 stateful · 2026-09-05 00:11:56 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,039,486
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
updatePrices
#4
0xab083028
#5
execOrders
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0x59558d29
#9
setData
#10
placeBet
#11
0xed82b078
#2
execOrders
#6
execOrders
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
0xfd713bab…a651
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x8feb2121…031a
0x34b655…2a6f
4 touches
1 conflict
0x9d7ac3b9…22f8
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc08f5302…7ed6
0x34b655…2a6f
4 touches
1 conflict
0xc52785b9…08f8
0x34b655…2a6f
4 touches
1 conflict
0xf7772b49…fc12
0x34b655…2a6f
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
0xfd713bab1a…98a651
Audit this contract →
← previous block
·
next block →
recent activity