pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,563,041
← previous block
next block →
recent activity
Analyzing
Block #98,563,041
11 transactions · 11 stateful · 2026-08-23 19:44:01 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,563,041
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x59558d29
#3
0x928e4afa
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
#6
setData
#7
0x3f5c179b
#8
claim
· blocks 1
#10
0x6a8b4df9
#9
0xc925b3a5
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
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x07880b9e…01c5
0x8964d7…10f8
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x07880b9e…01c6
0x8964d7…10f8
3 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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:
0x8964d7c9…5b10f8
1 conflict on slot
0x0000000000…000008
Audit this contract →
← previous block
·
next block →
recent activity