pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#109,143,084
← previous block
next block →
recent activity
Analyzing
Block #109,143,084
10 transactions · 10 stateful · 2026-09-29 21:27:10 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#109,143,084
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
permit2TransferAndMulticall
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x84403c1b
#5
0x013b6436
#6
0x013b6436
#7
setData
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ae9e2da…3e37
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x7dd96c96…7335
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x856d36e4…f467
0x5a66a5…cba8
2 touches
0 conflicts
0x00000000…0003
0x98a45d…206a
2 touches
0 conflicts
0x00000000…0004
0x98a45d…206a
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
0x3ae9e2da5c…ef3e37
Audit this contract →
← previous block
·
next block →
recent activity