pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,444,271
← previous block
next block →
recent activity
Analyzing
Block #76,444,271
14 transactions · 11 stateful · 2026-05-23 08:48:50 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,444,271
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
_makeSwaps
#4
execute
#5
revealWithCallback
#6
swap
#7
updateDataFeedsValuesPartial
#8
0x98717539
#9
0xed82b078
· blocks 1
#11
createModule
#12
0xe8891658
#13
setData
#10
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3003b0c8…8eaf
0x065c9d…c394
2 touches
0 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0000
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…0001
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…000f
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:
0xa6afd386…b0d132
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity