pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,557,833
← previous block
next block →
recent activity
Analyzing
Block #97,557,833
12 transactions · 9 stateful · 2026-08-20 06:46:56 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,557,833
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x41a8f47c
· blocks 1
#2
0x0c7abd22
#3
0x0c7abd22
#6
0x32d01e04
#7
0xab083028
#8
0x3f5c179b
#9
execFwdPositionOpsV2
#10
setData
#11
0x59558d29
#4
0xab083028
· blocks 1
#5
0x32d01e04
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0xb64473b0…0d6f
0xc8689a…ee79
4 touches
1 conflict
0x0150b43c…71dc
0x40c49f…2af0
3 touches
1 conflict
0x00000000…0005
0x103de0…bb55
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x5d98f1…8bb2
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
1 conflict on slot
0x5581d709b4…95ab77
Audit this contract →
← previous block
·
next block →
recent activity