pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,553,498
← previous block
next block →
recent activity
Analyzing
Block #80,553,498
9 transactions · 8 stateful · 2026-06-11 09:38:03 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
#80,553,498
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
dagSwapByOrderId
#4
setData
#5
0x6a2a8273
#6
0xe9316489
· blocks 1
#8
0xc7e3ec2c
#7
0xe9316489
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38937ad6…57d8
0x96b79e…d00a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x7467907b…964b
0x0a3323…0a3c
2 touches
0 conflicts
0xb1632c2f…d991
0x0a3323…0a3c
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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:
0x96b79ef4…d2d00a
1 conflict on slot
0x38937ad63f…4557d8
Audit this contract →
← previous block
·
next block →
recent activity