pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,567,924
← previous block
next block →
recent activity
Analyzing
Block #106,567,924
12 transactions · 11 stateful · 2026-09-20 21:15:21 UTC
Parallelism
75
/100
Blocked
27
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,567,924
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 2
#2
0xab083028
· blocks 1
#4
execOrders
#5
0x5acec890
#7
0x5acec890
#9
0xed82b078
#10
setData
#11
execOrders
#3
0xab083028
#6
0x5acec890
· blocks 1
#8
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
6
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1a4b4833…cf01
0x34b655…2a6f
2 touches
0 conflicts
0x21e79ad8…c5db
0x34b655…2a6f
2 touches
0 conflicts
0x2f50c84a…3640
0x34b655…2a6f
2 touches
0 conflicts
0x48828733…fd48
0x34b655…2a6f
2 touches
0 conflicts
0x556beb43…e627
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
3 conflicts on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity