pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,483,820
← previous block
next block →
recent activity
Analyzing
Block #80,483,820
12 transactions · 11 stateful · 2026-06-11 01:53:45 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,483,820
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
_makeSwaps
· blocks 1
#3
0xab083028
#4
forward
#5
approve
#6
0x0c7abd22
#8
0x6a2a15a1
#9
0xe9316489
· blocks 1
#11
setData
#7
0x3f5c179b
#10
0xe9316489
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ea0a6bc…6a74
0x2a68ba…90c5
4 touches
1 conflict
0xa7d33e6c…1bb4
0x96b79e…d00a
4 touches
1 conflict
0x2c26f820…dc1f
0x851145…3f07
3 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0x78eb0de5…1db2
0x01bff4…1071
2 touches
0 conflicts
0x00000000…0000
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…0001
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…000c
0x2b37ef…0bdc
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
0x1ea0a6bc62…356a74
Audit this contract →
← previous block
·
next block →
recent activity