pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,256,416
← previous block
next block →
recent activity
Analyzing
Block #80,256,416
13 transactions · 8 stateful · 2026-06-10 00:38:16 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,256,416
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
forward
#4
updateDataFeedsValuesPartial
#5
0x98717539
#6
0x6a28b26f
#7
0x3f5c179b
#8
0x6a28b26f
#9
0x6a28b26f
#10
setData
#11
0x8a1d24…385a
#12
0xb59071…3dad
#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
0x179fe783…6945
0xa6afd3…d132
4 touches
1 conflict
0x8cf3d245…1d0d
0x69df8a…6292
4 touches
1 conflict
0xb05cd4f5…73d0
0x69df8a…6292
4 touches
1 conflict
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0xdb067026…9eb8
0x69df8a…6292
4 touches
1 conflict
0xa973fa68…f94d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
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:
0xa6afd386…b0d132
1 conflict on slot
0x179fe7837f…326945
Audit this contract →
← previous block
·
next block →
recent activity