pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,224,897
← previous block
next block →
recent activity
Analyzing
Block #76,224,897
9 transactions · 8 stateful · 2026-05-22 08:28:16 UTC
Parallelism
56
/100
Blocked
38
%
Avg conflicts / tx
0.67
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,224,897
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execute
· blocks 3
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
#7
0x0f6795d9
#8
setData
#2
execute
· blocks 2
#3
execute
· blocks 1
#4
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12309510…0ac2
0x000000…012a
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x33018431…8f5c
0x188d58…ea8e
8 touches
6 conflicts
0x33018431…8f5d
0x188d58…ea8e
6 touches
3 conflicts
0x14ba0e5f…a74a
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5e
0x188d58…ea8e
2 touches
0 conflicts
0x301e1c77…9e30
0x34b655…2a6f
2 touches
0 conflicts
0x306093b7…287b
0x34b655…2a6f
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)
6 conflicts on slot
0x12309510bf…250ac2
Audit this contract →
← previous block
·
next block →
recent activity