pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,733,026
← previous block
next block →
recent activity
Analyzing
Block #98,733,026
11 transactions · 9 stateful · 2026-08-24 10:23:09 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,733,026
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xf78cb219
· blocks 2
#2
0xd524a9da
#4
execOrders
#5
0x59558d29
#6
forward
#8
0x62be7533
#9
0xed82b078
#10
setData
#3
0xab083028
· blocks 1
#7
0xe3a3c9cc
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xaa745789…e61e
0x065c9d…c394
4 touches
1 conflict
0xe49b1b9b…0be1
0x2b46c0…1669
2 touches
0 conflicts
0x6237f1a7…2f59
0x3bd359…433a
2 touches
0 conflicts
0x6d352690…6b75
0x3bd359…433a
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x00000000…0000
0x47bae1…7568
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
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity