pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#81,408,265
← previous block
next block →
recent activity
Analyzing
Block #81,408,265
9 transactions · 8 stateful · 2026-06-15 08:35:06 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
#81,408,265
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
· blocks 1
#2
0x1a945f9c
#4
0xed82b078
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a2fb9b2
#8
setData
#3
0x3f5c179b
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
0xef05b756…d18f
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92206814…ec27
0x1efe02…37d6
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x61218f00…5108
0x69df8a…6292
2 touches
0 conflicts
0xd8fd2add…50fc
0x69df8a…6292
2 touches
0 conflicts
0x8d0d8061…d410
0xc8689a…ee79
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:
0x851145ea…9f3f07
1 conflict on slot
0xef05b756a4…f6d18f
Audit this contract →
← previous block
·
next block →
recent activity