pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,137,213
← previous block
next block →
recent activity
Analyzing
Block #84,137,213
9 transactions · 7 stateful · 2026-06-28 00:08:13 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,137,213
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb5ce855a
#2
0xa96df62f
#3
0xab083028
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x98717539
#7
0xed82b078
#8
setData
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x352d1ab5…78d5
0x0a4fcb…a602
2 touches
0 conflicts
0xe4e96787…8e08
0x0a4fcb…a602
2 touches
0 conflicts
0xe4e96787…8e09
0x0a4fcb…a602
2 touches
0 conflicts
0xe4e96787…8e0a
0x0a4fcb…a602
2 touches
0 conflicts
0x6bd9b2de…7d72
0x0f2610…0edc
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
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity