pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,224,893
← previous block
next block →
recent activity
Analyzing
Block #76,224,893
11 transactions · 7 stateful · 2026-05-22 08:28:14 UTC
Parallelism
82
/100
Blocked
29
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,224,893
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#3
updatePrices
· blocks 1
#5
0x0d00188d
#6
0x5bf9264c
#7
0x5bf9264c
#8
updateDataFeedsValuesPartial
#9
0xf247d4…b26f
#10
setData
#2
0x9609049f
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x14ba0e5f…a748
0x188d58…ea8e
2 touches
0 conflicts
0x14ba0e5f…a749
0x188d58…ea8e
2 touches
0 conflicts
0x14ba0e5f…a74b
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5c
0x188d58…ea8e
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:
AUSD (AUSD)
1 conflict on slot
0x12309510bf…250ac2
Audit this contract →
← previous block
·
next block →
recent activity