pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,053,542
← previous block
next block →
recent activity
Analyzing
Block #106,053,542
14 transactions · 13 stateful · 2026-09-19 02:06:31 UTC
Parallelism
86
/100
Blocked
15
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,053,542
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ea3e879
#2
matchOrders
#3
0x5acec890
· blocks 1
#4
0xab083028
#6
0x5acec890
#7
0x59558d29
· blocks 1
#9
execPerpOps
#10
execPerpOps
#11
artefact_keep
#12
0x3f5c179b
#13
setData
#5
0x928e4afa
#8
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x0453e0dd…e8fd
0x6f6493…b480
2 touches
0 conflicts
0x0880d342…329e
0x6f6493…b480
2 touches
0 conflicts
0x1119beb9…c58c
0x6f6493…b480
2 touches
0 conflicts
0x20345fdf…4171
0x6f6493…b480
2 touches
0 conflicts
0x26183898…7a58
0x6f6493…b480
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
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity