pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,566,526
← previous block
next block →
recent activity
Analyzing
Block #108,566,526
13 transactions · 12 stateful · 2026-09-27 20:58:23 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
#108,566,526
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x59558d29
#3
0xab083028
#4
0xab083028
#5
execOrder
· blocks 1
#6
0x5acec890
#7
execFwdPositionOpsV2
#8
execOrders
#9
execFwdPositionOpsV2
#10
setData
#12
0x0c7abd22
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0xa69bb4e1…f2bb
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x213ee207…a151
0x34ae4d…3fc5
2 touches
0 conflicts
0x4014f822…6a2f
0x34b655…2a6f
2 touches
0 conflicts
0x52f1ec89…6777
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
0x7bd229ade5…6b63b2
Audit this contract →
← previous block
·
next block →
recent activity