pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,087,776
← previous block
next block →
recent activity
Analyzing
Block #99,087,776
12 transactions · 12 stateful · 2026-08-25 16:14:47 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,087,776
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
0x59558d29
#4
execFwdPositionOpsV2
#5
0x3f5c179b
#6
0x3f5c179b
#7
executeBatch
· blocks 1
#9
0xed82b078
#10
0x6a8dbfef
#11
setData
#8
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f18f001…2c08
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x8a87bc2c…313c
0xe52b14…7230
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x059e0ac0…0267
0x34b655…2a6f
2 touches
0 conflicts
0x1c2f0c4c…9bca
0x34b655…2a6f
2 touches
0 conflicts
0x1cb7e55e…b746
0x34b655…2a6f
2 touches
0 conflicts
0x377ca35b…e549
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:
0xe52b1424…bb7230
1 conflict on slot
0x1f18f00103…dd2c08
Audit this contract →
← previous block
·
next block →
recent activity