pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,327,738
← previous block
next block →
recent activity
Analyzing
Block #80,327,738
11 transactions · 6 stateful · 2026-06-10 08:33:48 UTC
Parallelism
82
/100
Blocked
17
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,327,738
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
0x98717539
#4
0x6a2921e4
#5
setData
#6
0xd30ae3…949c
#7
0xb3bf80…bb8b
#8
0xd2a174…17ec
#9
0x47d18a…7d21
#10
0x8c82d1…b2bf
#2
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
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
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3582f016…f3ca
0x065c9d…c394
2 touches
0 conflicts
0x63c93e8b…20d9
0x065c9d…c394
2 touches
0 conflicts
0xc39a6c2c…9810
0x065c9d…c394
2 touches
0 conflicts
0xcf79c9bd…4d39
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
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity