pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,019,462
← previous block
next block →
recent activity
Analyzing
Block #98,019,462
9 transactions · 7 stateful · 2026-08-21 21:55:59 UTC
Parallelism
56
/100
Blocked
57
%
Avg conflicts / tx
0.56
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,019,462
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execOrders
· blocks 1
#2
0xab083028
· blocks 2
#5
0xab083028
#6
0x0c7abd22
#3
0xab083028
· blocks 1
#8
execOrders
#4
0xab083028
· blocks 1
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w2
7
w3
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x41be9e75…9773
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x55012d1a…3907
0x2b46c0…1669
2 touches
0 conflicts
0xad3ef711…4f2b
0x2b46c0…1669
2 touches
0 conflicts
0xb8fccd1b…b5f2
0x2b46c0…1669
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