pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,654,024
← previous block
next block →
recent activity
Analyzing
Block #98,654,024
9 transactions · 8 stateful · 2026-08-24 03:37:55 UTC
Parallelism
56
/100
Blocked
50
%
Avg conflicts / tx
0.56
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,654,024
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x41a8f47c
· blocks 2
#2
0x41a8f47c
#6
execOrders
#8
forward
#3
0xab083028
· blocks 2
#4
0xab083028
· blocks 1
#5
0x8263f5d9
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0xb64473b0…0d6f
0xc8689a…ee79
4 touches
1 conflict
0xa13d9f68…32ee
0x065c9d…c394
3 touches
1 conflict
0xe2745681…ff50
0x3bd359…433a
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x13477596…b14c
0x754704…b603
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