pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,837,418
← previous block
next block →
recent activity
Analyzing
Block #98,837,418
8 transactions · 8 stateful · 2026-08-24 19:08:41 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,837,418
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x41a8f47c
· blocks 2
#2
setData
#4
0x0c7abd22
#5
0x59558d29
#7
execFwdPositionOpsV2
#3
0xab083028
· blocks 1
#6
0xe3a3c9cc
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x8e66da19…66b6
0x065c9d…c394
4 touches
1 conflict
0xd14ac7f4…c189
0x065c9d…c394
3 touches
1 conflict
0x2a354a63…0515
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x9193d0ca…ebff
0x065c9d…c394
2 touches
0 conflicts
0xa5ea523d…f472
0x065c9d…c394
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:
Kuru Exchange: MarginAccount
3 conflicts on slot
0x1125877469…519892
Audit this contract →
← previous block
·
next block →
recent activity