pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,549,113
← previous block
next block →
recent activity
Analyzing
Block #108,549,113
14 transactions · 13 stateful · 2026-09-27 19:30:32 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,549,113
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x59558d29
· blocks 1
#4
0xa96df62f
#5
updateDataFeedsValuesPartial
#6
poke
#7
resolveRound
#8
0xed82b078
#9
batchUpdate
#10
setMerkleRoot
#11
setData
#12
0x61d59c2d
#13
0x61d59c2d
#3
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0215d8e5…68d5
0x34b655…2a6f
2 touches
0 conflicts
0x06a0db59…5a3e
0x34b655…2a6f
2 touches
0 conflicts
0x30d077fe…181f
0x34b655…2a6f
2 touches
0 conflicts
0x5c1cc07a…b400
0x34b655…2a6f
2 touches
0 conflicts
0x625c4ed4…16aa
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004c
Audit this contract →
← previous block
·
next block →
recent activity