pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,265,870
← previous block
next block →
recent activity
Analyzing
Block #96,265,870
9 transactions · 6 stateful · 2026-08-15 17:42:03 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,265,870
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf5e395a
· blocks 1
#2
0x4f819052
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x62be7533
#8
setData
#3
0x6ad2e98b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0001
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0003
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0009
0x04ddf6…7f33
2 touches
0 conflicts
0x0b9c8607…5ee7
0x065c9d…c394
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
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity