pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,538,806
← previous block
next block →
recent activity
Analyzing
Block #98,538,806
12 transactions · 10 stateful · 2026-08-23 17:37:30 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,538,806
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6ad2e98b
#3
0xab083028
#4
0x59558d29
#5
execPerpOps
#6
execPerpOps
#7
setData
#8
execFwdPositionOpsV2
#9
0xaf47a8bb
· blocks 1
#11
execOrders
#10
0x5de3085d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x65d862…09f4
4 touches
1 conflict
0x01ad188c…9b7f
0x91b81b…6d56
4 touches
1 conflict
0x82d396a1…2adb
0x91b81b…6d56
4 touches
1 conflict
0x843d1c63…21ce
0x91b81b…6d56
4 touches
1 conflict
0x962f9067…c207
0xb0a788…7777
4 touches
1 conflict
0x9dd37003…3b83
0xe1c8b7…3022
4 touches
1 conflict
0xb8818aed…0072
0xe1c8b7…3022
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
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:
0x65d86244…f709f4
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity