pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,566,425
← previous block
next block →
recent activity
Analyzing
Block #92,566,425
9 transactions · 8 stateful · 2026-08-02 18:59:37 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,566,425
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe33905c2
#2
0x39435dac
#3
updateDataFeedsValuesPartial
#4
0x7c51d6cf
· blocks 1
#6
0x0f6795d9
#7
setData
#8
0x59558d29
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xb0193c15…523b
0x40c49f…2af0
3 touches
1 conflict
0x087dd6f4…b500
0x34b655…2a6f
2 touches
0 conflicts
0x0c119c6d…a42e
0x34b655…2a6f
2 touches
0 conflicts
0x2002baa3…b2ec
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x786abcf3…01e8
0x34b655…2a6f
2 touches
0 conflicts
0x923c57f1…7810
0x34b655…2a6f
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
0x002fed350f…7379fa
Audit this contract →
← previous block
·
next block →
recent activity