pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,113,157
← previous block
next block →
recent activity
Analyzing
Block #108,113,157
12 transactions · 12 stateful · 2026-09-26 06:56:22 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
#108,113,157
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x3f5c179b
#3
0x84403c1b
· blocks 1
#5
resolveRound
#6
forward
#7
execFwdPositionOpsV2
#8
0x6ab76c99
#9
setData
#10
execOrders
· blocks 1
#4
0x84403c1b
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35dcf126…5313
0x34b655…2a6f
4 touches
1 conflict
0x3b8da5cc…e045
0x34b655…2a6f
4 touches
1 conflict
0x532af68d…503d
0x34b655…2a6f
4 touches
1 conflict
0x866110ca…7080
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x7cfdc4…1fbd
2 touches
0 conflicts
0x00000000…003d
0x851145…3f07
2 touches
0 conflicts
0x00000000…003d
0xa6afd3…d132
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
0x35dcf126e0…085313
Audit this contract →
← previous block
·
next block →
recent activity