pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,328,983
← previous block
next block →
recent activity
Analyzing
Block #80,328,983
12 transactions · 9 stateful · 2026-06-10 08:42:05 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,328,983
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
#2
0x0f6795d9
#3
execute
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x794239…c728
#9
0xab0677…50b2
#10
0xc7e3ec2c
#11
0xc7e3ec2c
#4
execute
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
0x00000000…0001
0x24b18e…3301
4 touches
1 conflict
0x771a3650…01cd
0x3bd359…433a
4 touches
1 conflict
0x797464db…e15a
0x788571…8888
4 touches
1 conflict
0xa743c8dd…ebf2
0x788571…8888
4 touches
1 conflict
0x00000000…0000
0x24b18e…3301
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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:
0x24b18eb6…733301
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity