pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,854,704
← previous block
next block →
recent activity
Analyzing
Block #99,854,704
10 transactions · 10 stateful · 2026-08-28 08:48:08 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
#99,854,704
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0xab083028
#3
0x59558d29
#4
execOrders
· blocks 1
#6
relay
#7
execFwdPositionOpsV2
#8
setData
#9
execOrders
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0x8f4be1ed…2e29
0x34b655…2a6f
4 touches
1 conflict
0xf74d1ad7…4e94
0x34b655…2a6f
4 touches
1 conflict
0x08d53462…97ef
0x2b46c0…1669
2 touches
0 conflicts
0x12f129f2…fe6b
0x2b46c0…1669
2 touches
0 conflicts
0x5a409e7f…09b6
0x2b46c0…1669
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
0x31d88d27c1…837617
Audit this contract →
← previous block
·
next block →
recent activity